AshleyK

Group: Members
Posts: 11
Joined: Oct. 2003 |
 |
Posted: Dec. 30 2003,22:11 |
 |
I've been using DSL on my second PC for a little while at the 0.4.8 release and today installed the 5.1.1 release 'cus I notice that nfs is supported. Sure enough I can now mount an NFS volume on my server which is a great step forward. But, (and there always is one)... try as I might I cannot get an automount at system boot to work. I particularly want to get the server based home directories useable by the client machine. This is what I have so far:
On 'nfs server' I have /home exported to my own network (nnn.nnn.nnn.*) as rw (read/write). When I do a mount -t nfs <server>:/home /home on the client PC as root /home gets mapped to the remote server as expected.
I added : <server>:/home /home nfs nfsvers=3,rw 0 0 to the /etc/fstab file on the client and rebooted
ls /home reveals that I am still mapped to my local machine, not the server.
I tried to see if autofs (also part of DSL distro) could do anything but frankly, having read through three howtos I can make no sense of it whatsoever.
Suggestions greatfully received.
Ashley
|