Quote:
dmask=777,fmask=777,umask=000
|
The dmask and fmask allow you to use different permissions for files then for directories. This allows you to mask out the X bit for files but not for directories. Your fmask and dmask are wrong however, but the umask changes the permissions for everything.
You could use dmask=000,fmask=111 and not use umask. The mask bits deny permissions.
Also double check whether your kernel supports cifs instead of smbfs. The smbfs kernel module is being superceded by the cifs module which has better Linux/Unix to Linux/Unix features.
It may be better to use a credentials file, containing the username and password. Issuing a mount command with the password makes it visible to other uses.
Code:
//192.168.1.15/media smbfs /mnt/Network/Fileserver smbfs username=blah,password=blah,dmask=777,fmask=777,umask=000 0 0
You might also want to use the noauto option so the system doesn't try to mount the partition on boot. There is a
_netdev option which delays mounting until the network is up, but if the host at 192.168.1.15 is down you might still have a problem.
The fstab file has its own manpage as well: man 5 fstab
If you have the kernel source installed, look in the Documentation/filesystems/ directory for a cifs.txt file.