I've redesigned my home lan to have a slack box with some big storage that my other slack box(s) and a WinXp machine share and GigE to move things around. I quickly hit the 2GB smbfs limitation copying around some DVD images. Opps. So I googled a bit and found CIFS.
From my reading I believe it is correct that the kernel option for cifs is needed on the client only. So I went and recompiled my kernel, 2.6.15.1, with the cifs option (and statistics just for fun) and tried changing my fstab to use cifs.
The two slackware 10.2 boxes in question here are moat, the server, and tower, the client, each running 2.6.15. Each are identified correctly in thier respective /etc/hosts file.
This is the old samba mount:
Code:
//moat/safe /safe smbfs credentials=/etc/samba/moat_credentials,rw 1 1
and works fine (right up to 2G).
This is the modified cifs mount
Code:
//moat/safe /safe cifs credentials=/etc/samba/moat_credentials,rw 1 1
This wont mount.
Code:
root@tower:/etc/samba# mount /safe
mount: wrong fs type, bad option, bad superblock on //moat/safe,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
syslog says:
Code:
Jan 25 08:36:58 tower kernel: CIFS VFS: No username specified
Jan 25 08:36:58 tower kernel: CIFS VFS: cifs_mount failed w/return code = -22
The things I've been reading say this should pretty much work? Do I need to compile cifs on the server as well? What's the simple step I seem to have missed? (it's always the little things...)