lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <524f69650801301854p5d095233kfebabcfc41b00be4@mail.gmail.com>
Date:	Wed, 30 Jan 2008 20:54:06 -0600
From:	"Steve French" <smfrench@...il.com>
To:	"Jan Engelhardt" <jengelh@...putergmbh.de>
Cc:	"David Newall" <davidn@...idnewall.com>,
	"Adrian Bunk" <bunk@...nel.org>, sfrench@...ba.org,
	samba-technical@...ts.samba.org, linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] remove smbfs

On Jan 30, 2008 8:23 PM, Jan Engelhardt <jengelh@...putergmbh.de> wrote:
>
>
> On Jan 31 2008 12:33, David Newall wrote:
> >Jan Engelhardt wrote:
> >> On Jan 30 2008 12:53, Steve French wrote:
> >>
> >>> I have mounted to Windows98 a few months ago with no problems (other
> >>> than a few restrictions like you can't set the file times via utimes).
> >>> For mounts to Windows98 note that you have to specify the server
> >>> netbios name on the mount (since it is not the same as the DNS name).
> >>> In your example your would need to specify "servernetbiosname=WIN98"
> >>> in the mount options (until mount.cifs autoretries with
> >>> servernetbiosname assumed to be the beginning of the UNC name - note
> >>> that later servers have a dummy netbios name that is used so this
> >>> mount option is only needed for OS/2 and Win9x).
> >>
> >> Ok that works. I had tried "netbiosname" but not "servernetbiosname"
> >> (only fuzzy memories from the last win98 encounter and the suggestion
> >> to use netbiossomething).
> >
> >Apparently CIFS lacks an adequate man page (otherwise Jan would have
> >discovered servernetbiosname for himself.)  That's sufficient reason to
> >keep smbfs, and just to be radical, why not remove cifs until it's
> >properly documented?  Man pages are essential.

The cifs user guide (note that smbfs did not have a user's guide) does
list the required mount options pretty clearly in the section on mount
syntax on page 4.   Excerpt follows:

mounting to older servers (those prior to1997) may require specifying
two additional fields beyond
those which smbfs required:
a) The server's netbios (RFC1001) name AND the server's tcp (or ip )
address. CIFS does not
assume, as smbfs did, that the tcp name and the netbios name of the
server are the same. The netbios name of the server is specified by
passing the mount option "servern=SERVERNAME" and is not assumed to be
necessarily the same as the tcp name of the server (also note that the
netbios name is usually capitalized). Both tcp/ip name and netbios
name have to be specified for mounts for most old lanman servers. For
example:
         mount -t cifs //tcp-name-of-server/sharename



Current versions of "mount.cifs -h" also list all mount options, and
the README information on the syntax is also current and contains
information which needs to be added to the mount.cifs man page.   I
will make this fix for the mount.cifs man page, it lags behind the
mount.cifs help and the README but any additional updates to the man
page text to clarify it would be welcome.

> smbfs does not seem to do NT/XP mounts, so that's kinda problematic
> too, as fun as it sounds :)





-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ