[opensuse] The smbfs/cifs fiasco in 10.2
What is the current thinking on the smbfs/cifs fiasco in 10.2? Like many other people, when I try to use smbmount I get the message: suillus:~ # smbmount //lactarius/ext-backup mnt Password: ERROR: smbfs filesystem not supported by the kernel Please refer to the smbmnt(8) manual page smbmnt failed: 255 smbmount worked just fine in previous releases. Some research told me that I should be using cifs instead, and I got this (from a root shell): suillus:~ # mount.cifs //lactarius/dext-backup.mnt mount error: could not find target server. TCP name lactarius/ext-backup not found No ip address specified and hostname not found Yet I can see smb://lactarius/ext-backup from Konqueror. What's particularly puzzling is that if I do the same thing from the lactarius machine, it does the mount correctly. On the other hand, from lactarius I get the error if I try to mount a suillus SMB share. In other words, the error appears if you try to use mount.cifs for a file on some other machine but not if you use it for a file on your own machine. There's lots of stuff posted about this problem in various places but no clear, agreed-upon solution that I've seen. Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Paul Abrahams wrote:
What is the current thinking on the smbfs/cifs fiasco in 10.2? Like many other people, when I try to use smbmount I get the message:
suillus:~ # smbmount //lactarius/ext-backup mnt Password: ERROR: smbfs filesystem not supported by the kernel Please refer to the smbmnt(8) manual page smbmnt failed: 255
smbmount worked just fine in previous releases. Some research told me that I should be using cifs instead, and I got this (from a root shell):
suillus:~ # mount.cifs //lactarius/dext-backup.mnt mount error: could not find target server. TCP name lactarius/ext-backup not found No ip address specified and hostname not found
I had same problem smbfs not supported by kernel. Just replaced smb with cifs and it worked as before. Not really a fiasco in my book, I mount loads of Windows drives from all over, not had a problem other than that. Matthew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 02 March 2007 4:33 pm, Matthew Stringer wrote:
Paul Abrahams wrote:
smbmount worked just fine in previous releases. Some research told me that I should be using cifs instead, and I got this (from a root shell):
suillus:~ # mount.cifs //lactarius/ext-backup.mnt mount error: could not find target server. TCP name lactarius/ext-backup not found No ip address specified and hostname not found
I had same problem smbfs not supported by kernel. Just replaced smb with cifs and it worked as before.
Not for me -- see the last part of my original post, repeated above.
Not really a fiasco in my book, I mount loads of Windows drives from all over, not had a problem other than that.
It's a fiasco because (a) I'm not the only one who's not been able to solve this, and (b) the original message about smbfs not being supported in the kernel is wildly misleading, especially if you've had it working in a previous SuSE version. Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Mar 02, 2007 at 05:25:56PM -0500, Paul Abrahams wrote:
this, and (b) the original message about smbfs not being supported in the kernel is wildly misleading, especially if you've had it working in a previous SuSE version.
The note about smbfs is probably correct: $ gzip -cd /proc/config.gz | grep -i smb # CONFIG_SMB_FS is not set $ gzip -cd /proc/config.gz | grep -i cifs CONFIG_CIFS=m CONFIG_CIFS_STATS=y CONFIG_CIFS_STATS2=y CONFIG_CIFS_WEAK_PW_HASH=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set # CONFIG_CIFS_EXPERIMENTAL is not set $ uname -a Linux haldeman 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 i686 athlon i386 GNU/Linux $ Feel free to check your own system to validate.
On Friday 02 March 2007 5:25 pm, I wrote:
It's a fiasco because (a) I'm not the only one who's not been able to solve this, and (b) the original message about smbfs not being supported in the kernel is wildly misleading, especially if you've had it working in a previous SuSE version.
One more thing. The error message also says: Please refer to the smbmnt(8) manual page That makes it even more misleading since there's nothing on that manpage that helps. Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007/03/02 15:07 (GMT-0500) Paul Abrahams apparently typed:
What is the current thinking on the smbfs/cifs fiasco in 10.2? Like many other people, when I try to use smbmount I get the message: ... There's lots of stuff posted about this problem in various places but no clear, agreed-upon solution that I've seen.
CIFS wasn't, and isn't, ready to replace SMBFS. CIFS remains very buggy, and virtually useless on networks that include W9x and OS/2 LM servers. The only solution for me is recompile post-2.6.17 kernels with SMBFS enabled. -- "For God did not send his Son into the world to condemn the world, but to save the world through him." John 3:17 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 03 March 2007 00:12, Felix Miata wrote:
On 2007/03/02 15:07 (GMT-0500) Paul Abrahams apparently typed:
What is the current thinking on the smbfs/cifs fiasco in 10.2? Like many other people, when I try to use smbmount I get the message:
...
There's lots of stuff posted about this problem in various places but no clear, agreed-upon solution that I've seen.
CIFS wasn't, and isn't, ready to replace SMBFS. CIFS remains very buggy, and virtually useless on networks that include W9x and OS/2 LM servers. The only solution for me is recompile post-2.6.17 kernels with SMBFS enabled.
As James Parra said, use the IP addres of the machine instead of the computer's name. The error message you get even says to use the IP address. - James W -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
As James Parra said, use the IP addres of the machine instead of the computer's name. The error message you get even says to use the IP address.
- James W
sooo what to do with dynamic ip addressing? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
kanenas@hawaii.rr.com skrev:
As James Parra said, use the IP addres of the machine instead of the computer's name. The error message you get even says to use the IP address.
- James W
sooo what to do with dynamic ip addressing?
Don't use dynamic addressing? -- Anders Norrbring Norrbring Consulting
kanenas@hawaii.rr.com skrev:
On Sunday 04 March 2007, Anders Norrbring wrote:
Don't use dynamic addressing?
just because, eh? wonderful...
Seriously, if you have to address with IP and not mapped names, then you can write a couple of small scripts that reports the current IP to the machine that needs it. It shouldn't be too hard. -- Anders Norrbring Norrbring Consulting
On Sunday 04 March 2007 5:08 am, Anders Norrbring wrote:
kanenas@hawaii.rr.com skrev:
As James Parra said, use the IP addres of the machine instead of the computer's name. The error message you get even says to use the IP address.
- James W
sooo what to do with dynamic ip addressing?
Don't use dynamic addressing?
Maybe it's just an aesthetic issue, but this kind of workaround shouldn't be necessary even if it does work. Dynamic addressing was no problem in earlier versions of SuSE; this sort of degraded functionality is unpleasant and unsatisfying even if it's possible to bypass it by ad-hoc measures. Paul -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
kanenas@hawaii.rr.com wrote:
sooo what to do with dynamic ip addressing?
If you control the DHCP server, you could tell it to nail that machine down to a specific IP. That's what I do with all of mine. I don't like doing file sharing between dynamically-addressed machines; it seems like asking for trouble. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-03-02 14:07, Paul Abrahams wrote:
<snip>
suillus:~ # mount.cifs //lactarius/dext-backup.mnt mount error: could not find target server. TCP name lactarius/ext-backup not found No ip address specified and hostname not found
Yet I can see smb://lactarius/ext-backup from Konqueror.
<snip> See file /usr/src/linux/fs/cifs/README for useful information on using cifs, particularly the remark about adding "unix extensions = yes" to the smb.conf file on the server side. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Anders Norrbring -
Darryl Gregorash -
David Brodbeck -
Felix Miata -
James Wright -
kanenas＠hawaii.rr.com -
Matthew Stringer -
Paul Abrahams -
Seth Arnold