This is a discussion on [Samba] mount.cifs issues - Samba ; There are some aspects of mount.cifs behavior on Fedora 7 that do not matchthe documentation for mount.cifs, including the Linux CIFS Client Guide, or do not match the Windows client. 1.) In the credentials file, shortforms of the "username" and ...
There are some aspects of mount.cifs behavior on Fedora 7 that do not matchthe documentation for mount.cifs, including the Linux CIFS Client Guide, or do not match the Windows client.
1.) In the credentials file, shortforms of the "username" and "password" keywords are not recognized. Credentials given with the long from keywords work fine. Also, spaces around the equals sign cause the keywords to go unrecognized.
2.) If a UNC name represents a subfolder of a server share (e.g., //serverName/shareName/subfolderName), BUT with backslashes replaced by forward slashes, the resource is mounted correctly, but /proc/mounts and friends show the mount device as being the share. If the UNC is given with backslashes, then only the top-level share can be mounted.
3.) //serverName/shareName/subfolderName/subsubfolderName cannot be mounted. However, the Windows networking client does mount a UNC repesenting a 2-deep subfolder of a share.
It would be useful to be able to mount subfolders of shares, so that different folders can be mounted with different permissions, adding a layer of protection on the Unix side (for protection against errant backup scripts, for example).
PS: 1.) In Windows Explorer, the menuaction Tools->Map Directory allows a drive mapping to be assigned to a UNCrepresenting a 3-deep subfolder of a server share.
2.) The Linux CIFS Client Guide referenced is: http://pserver.samba.org/samba/ftp/c...ient-guide.pdf
Pinpoint customers who are looking for what you sell.
To unsubscribe from this list go to the following URL and read the