public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Langasek <vorlon@debian.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: sfrench@samba.org, samba-technical@lists.samba.org,
	linux-kernel@vger.kernel.org, Jeff Layton <jlayton@redhat.com>
Subject: Re: [2.6 patch] remove smbfs
Date: Wed, 30 Jan 2008 17:34:15 -0800	[thread overview]
Message-ID: <20080131013415.GA3768@dario.dodds.net> (raw)
In-Reply-To: <20080131004717.GX29368@does.not.exist>

On Thu, Jan 31, 2008 at 02:47:17AM +0200, Adrian Bunk wrote:
> > smbfs has the unfortunate quality of momentum. A lot of users aren't
> > aware of CIFS at all since smbfs basically does what they need it to
> > do. Some extra warning for those users would be nice.

> And many users will start whining loudly that the not deprecated driver 
> (in this case cifs) has this or that bug not before the patch to finally 
> remove the deprecated feature got applied or at least posted.

> And will demand that it therefore does not get removed.

We've had about 3 of these in Debian since deciding to cut it from the
upcoming release.  (The kicker for us was the samba security update that
wasn't tested with smbfs as a client.)  The key regressions of interest
relative to smbfs seem to be:

- lack of DFS support
- lack of netbios name resolution for UNC share names

The former seems to be a kernel issue whose resolution is in progress, and I
think the latter would have to be addressed in the userspace mount tools?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

  parent reply	other threads:[~2008-01-31  1:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 22:08 [2.6 patch] remove smbfs Adrian Bunk
2008-01-28 22:55 ` Steve French
2008-01-30 18:27 ` Jan Engelhardt
2008-01-30 18:53   ` Steve French
2008-01-30 19:05     ` Jan Engelhardt
2008-01-31  1:23       ` Steve French
2008-01-31 11:18         ` Jan Engelhardt
2008-01-31  2:03       ` David Newall
2008-01-31  2:23         ` Jan Engelhardt
2008-01-31  2:54           ` Steve French
2008-01-30 20:52     ` Guenter Kukkukk
2008-01-30 21:16 ` Guenter Kukkukk
2008-01-30 22:41   ` Jeff Layton
2008-01-30 22:58     ` Adrian Bunk
2008-01-31  0:34       ` Jeff Layton
2008-01-31  0:47         ` Adrian Bunk
2008-01-31  1:13           ` Jeff Layton
2008-01-31  1:30             ` Steve French
2008-01-31  8:26               ` Radoslaw Szkodzinski
2008-01-31  9:51               ` Andi Kleen
2008-01-31  1:34           ` Steve Langasek [this message]
2008-01-31  2:58             ` Steve French
2008-01-31  0:58     ` Lennart Sorensen
2008-02-05  8:18     ` Andrew Morton
2008-02-05 11:31       ` Jeff Layton
2008-02-05 18:17         ` Andrew Morton
2008-02-05 14:04       ` Alejandro Riveira Fernández
2008-02-05 14:58       ` Steve French

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080131013415.GA3768@dario.dodds.net \
    --to=vorlon@debian.org \
    --cc=bunk@kernel.org \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox