>> ... replacing "192.168.55.44" with the address of the laptop. > > [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit > mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 > mount.nfs: trying text-based options > 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' > < ... > > ^C > [root@localhost ~]#
I often get timeout (or never-completing mount) when some magical part of the RPC suite hasn't been started. The server will need at least 'rpc.mountd'. I think the client will need 'rpc.statd'. (I confess to not retaining these details.) Both are likely to need 'rpcbind'. > In case you're assuming I have two machines, > I have only the one Linux laptop, on which I've tried all suggestions so far. Yes, I was assuming that. Sorry to have missed that part. NFS mounting this content back on the laptop (from which it is served out) DOES answer the question if the NFS server software is working. Otherwise, it's not all that useful. > Should I be trying these mount commands from another machine, > e.g. the SLES install program on z/VM? I could also use one of the RHEL > identities on z/VM. Yes. As I recall, you're using this media hosted on the laptop to effect an install hosted on VM. So you'll eventually want an NFS client mount on the SLES installation target end. -- -- R; <>< ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
