hi to all. i have two machines 'A'(192.168.100.20) and 'B'(192.168.100.21) with dapper loaded.Both machines have two user accounts staff and student consequently i have a two directories /home/staff and /home/student on machine A as well as B.

Now i want these directories to be mounted by machine B at boot time in such way that if user logs in as staff on machine B he should have rw access to the mounted folder A:/home/staff and have no access to A:/home/student. similarly if user student logs in at B he should have rw access to A:/home/student but not to A:/home/staff.

i have installed and started portmap as well as nfs-kernel-server on A. i have also installed portmap and nfs-common on B. now everything works OK and if i mount thru terminal like this:
sudo mount 192.168.100.20:/home/staff /home/staff
it works ok.
but if i write this in /etc/fstab it does not mount the relevant files at boot time:
192.168.100.20:/home/staff /home/staff default 0 0
i mean i can mount manually but fstab entry is not working.
PLEASE HELP I HAVE BEEN ON THIS FOR A WEEK NOW.

it should be

spotted a typo. Make sure the filesystem type is nfs not ntfs.

should i write nfs or ntfs? and thanks for the defaults tip. Thanks a lot

nfs, nfs , nfs

ok nfs it shall be. and thanks a lot for such a quick response. hope i can help out others like this some day.

i checked my system fstab entry, there is nothing wrong with it. here is exact entry:
192.168.100.20:/home/staff /home/staff nfs defaults 0 0
192.168.100.20:/home/student /home/student nfs defaults 0 0
and it is not working. i ran showmount -e on server the output was the exported directories. i ran showmount on client it showed the result ok. the portmap is running on client. i donot know how to check if nfs-common is running. but if run mount commond thru terminal the directories get mounted. whats happening here? please help.

Have you checked your hosts file. For some reason my dhcp is not answering for the server name soon enough

I have the exact same problem. After boot mounting works, while putting it in fstab doesn't mount is successfully.

I've noticed that when I put the nfs line in fstab, portmap has a problem loading at boot.

Perhaps this happens because mount, when it reads the fstab line, acts different than typing mount ip:foo foo. Perhaps understanding how mount reads fstab will get me to the bottom of this...

I don't understand why this problem persists. I'm not looking further into this.

I've settled for the fstab line This way it doesn't mount at boot and my desktop environment allows me to easily mount it as a user.

Cheers!

Yes this thread is way old, but I have relevant info.

One thing to keep in mind when comparing commands in a virtual terminal to commands executed at startup from an fstab file is that the command syntax may be slightly different. So in a virtual terminal, if you had a dash(-) as part of a directory name, you might put it in quotes, /”Joe-Linux-NFS”/ . But with fstab, homey don't play that game-it might not won't work with the quotes, only without, /Joe-Linux-NFS/ .

I'm not sure how that plays with different issues like a space in the name. I think there you might have to put the entire directory in quotes with fstab. Trial and error, or get giggy with the manual.

Thanks all.

Be real, be sober.

I'm going to assume that you're using some flavor of Red Hat. If that's the case your fstab isn't the heart of the problem.

Try this:

# chkconfig --list netfs
netfs 0: off 1: off 2ff 3: on 4: on 5: on 6: off

If 3, 4, and 5 are set to 'off' then you've not asked the OS to automatically mount the NFS file systems.

Run this and you should be able to persist across a reboot.

# chkconfig --level 345 netfs on

2 members found this post helpful.

Having a dash in a directory name won't require escaping. You are right that bash isn't parsing the /etc/fstab file so you need to escape spaces in directory names as \040.

One could use the _netdev option in the fstab mount options. This allows the startup scripts to first mount local file mounts with "mount -a -O no_netdev", excluding nfs mounts. Then after the network is ready, it can mount those with _netdev entries.

Also be sure to check out automount, autofs and auto.master manpages. I think that autofs replaced netfs in recent kernels. Make sure you aren't using RH 9 which is obsolete and not secure.