http://qa.mandrakesoft.com/show_bug.cgi?id=5912
[EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From [EMAIL PROTECTED] 2003-22-09 17:38 ------- aleph-null:~# update-alternatives --display smbclient smbclient - status is auto. link currently points to /usr/bin/smbclient2 /usr/bin/smbclient2 - priority 10 slave nmblookup: /usr/bin/nmblookup2 slave mount.smb: /sbin/mount.smb2 slave cups_smb: /usr/lib/cups/backend/smb2 slave mount.cifs: /bin/mount.cifs2 slave smbprint: /usr/bin/smbprint2 slave smbumount: /usr/bin/smbumount2 slave smbspool: /usr/bin/smbspool2 slave smbmount: /usr/bin/smbmount2 slave mount.smbfs: /sbin/mount.smbfs2 slave smbtar: /usr/bin/smbtar2 slave findsmb: /usr/bin/findsmb2 slave smbmnt: /usr/bin/smbmnt2 Current `best' version is /usr/bin/smbclient2. aleph-null:~# ls -l /etc/alternatives/*smb* lrwxrwxrwx 1 root root 26 Sep 11 02:17 /etc/alternatives/cups_smb -> /usr/lib/cups/backend/smb2* lrwxrwxrwx 1 root root 17 Sep 11 02:17 /etc/alternatives/findsmb -> /usr/bin/findsmb2* lrwxrwxrwx 1 root root 16 Sep 11 02:17 /etc/alternatives/mount.smb -> /sbin/mount.smb2* lrwxrwxrwx 1 root root 18 Sep 11 02:17 /etc/alternatives/mount.smbfs -> /sbin/mount.smbfs2* lrwxrwxrwx 1 root root 19 Sep 11 02:17 /etc/alternatives/smbclient -> /usr/bin/smbclient2* lrwxrwxrwx 1 root root 16 Sep 11 02:17 /etc/alternatives/smbmnt -> /usr/bin/smbmnt2* lrwxrwxrwx 1 root root 18 Sep 11 02:17 /etc/alternatives/smbmount -> /usr/bin/smbmount2* lrwxrwxrwx 1 root root 18 Sep 11 02:17 /etc/alternatives/smbprint -> /usr/bin/smbprint2* lrwxrwxrwx 1 root root 18 Sep 11 02:17 /etc/alternatives/smbspool -> /usr/bin/smbspool2* lrwxrwxrwx 1 root root 16 Sep 11 02:17 /etc/alternatives/smbtar -> /usr/bin/smbtar2* lrwxrwxrwx 1 root root 19 Sep 11 02:17 /etc/alternatives/smbumount -> /usr/bin/smbumount2* However, /sbin/mount.smbfs didn't exist, which is where the problem was. Running the update-alternatives fixed the problem. I have marked as a duplicate of 5889. This will be fairly important for people on a windows network, with entries currently in /etc/fstab, or autofs for mounting windows servers. *** This bug has been marked as a duplicate of 5889 *** -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: I don't know if this bug should be kernel or samba-client. I am trying to mount a smb share on the network with the following command: aleph-null:/home/chrisp# mount -t smbfs //alisha/storage /mnt/smb -oip=192.168.10.23 mount: wrong fs type, bad option, bad superblock on //alisha/storage, or too many mounted file systems aleph-null:/home/chrisp# mount -t smbfs //aleph-null/downloads /mnt/smb -oip=192.168.10.23 mount: wrong fs type, bad option, bad superblock on //aleph-null/downloads, or too many mounted file systems The first machine is windows 2000, the second is the local machine (mandrake cooker) In my messages file I get: Sep 22 12:19:35 aleph-null kernel: smbfs: mount_data version 826110057 is not supported and when I try again, Sep 22 12:20:00 aleph-null kernel: smb_read_super: missing data argument I can however, use smbclient or nautilus to browse shares. Thanks Chris