The Howto states that the following kernel options need to be set. CONFIG_SMB_FS=m CONFIG_SMB_UNIX=y The first is obsolete and CONFIG_CIFS=m should be used, the second does not exist anymore in the kernel. All following mount commands must have a "-t cifs" instead of "-t smbfs", problem is that the mount.cifs utility is shipped with samba and needed. So the client must have samba installed (but not loaded as a daemon) or install net-fs/mount-cifs from the Sunrise overlay, which is a standalone version. The rest of the guide seems to be fine regarding CUPS and Samba as my network is just running smoothly, ClamAV has not been installed so I did not check that.
1. Which kernel version requires CONFIG_CIFS=m? Is it for a stable kernel? 2. Same with CONFIG_SMB_UNIX=y 3. When you say samba still has to be installed but not loaded as a daemon, do you mean that it should not be rc-updated to any runlevel? (i.e. don't do 'rc-update add foo default') 4. We cannot and will not recommend to our users to install unsupported software, especially from an overlay, so another solution must be found.
(In reply to comment #1) > 1. Which kernel version requires CONFIG_CIFS=m? Is it for a stable kernel? Yes. CONFIG_SMB_FS is still there but replaced by CIFS...this must be more than a year now. > 2. Same with CONFIG_SMB_UNIX=y It does not exist in Kernel 2.6.21 and .20 at least anymore. The last mentioning about it was about Kernel 2.4. > 3. When you say samba still has to be installed but not loaded as a daemon, do > you mean that it should not be rc-updated to any runlevel? (i.e. don't do > 'rc-update add foo default') Yes, on the client, not the server. > 4. We cannot and will not recommend to our users to install unsupported > software, especially from an overlay, so another solution must be found. Sure. That's true, it was only an alternative...either mount-cifs or samba on the client.
Thanks for reporting, fixed in CVS.
Thanks for the quick reaction, but there is still missing, that samba needs to be emerged on the client. "Mounting a Windows or Samba share in GNU/Linux" would be the right place to mention it.
Fixed, again.
