linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: John Kelly <jak@isp2dial.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree
Date: Fri, 12 May 2006 09:59:11 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605120949060.3866@g5.osdl.org> (raw)
In-Reply-To: <200605121630.k4CGUuiU005025@isp2dial.com>



On Fri, 12 May 2006, John Kelly wrote:
> 
> Users who need vintage features can use vintage kernels.  They haven't
> been pulled off the market.

I disagree.

We have two cases:

 - newer kernels don't always support vintage hardware any more. We don't, 
   for example, boot on 1MB PCs (I _think_ we used to), and quite frankly, 
   if you have 4MB, I'd be surprised it worked either (and that definitely 
   used to work a long time ago).

   Similarly, we've occsionally dropped a driver just because it wasn't 
   getting maintained, and we knew it couldn't work in the state it was 
   in. So over the years, machines have stopped being supported (that 
   said, if somebody complains, we try to re-instate the driver. Most 
   dropped drivers have never even been commented upon, because they 
   really aren't used any more. When was the last time you saw an MCA 
   machine or a PC98? I bet some people on this list have never even 
   heard of either)

 - we sometimes drop sw features that have been deprecated long ago, and 
   that there are better alternatives for. That said, this is pretty damn 
   rare too. I can remember Xiafs, and devfs is obviously on that path 
   too.

But we do _not_ drop features just because they are deemed "unnecessary". 
As long as somebody actually _uses_ smbfs, and as long as those users are 
willing to test and perhaps send in patches for when/if it breaks, we 
should not drop it.

The cost of keeping a filesystem is not normally very high. The way 
filesystems in particular get deprecated is if they have really serious 
problems, and nobody ends up being able or willing to fix them at all, and 
you _can_ migrate away. But if we're talking about win98, it probably 
still actually has a pretty big user base, and most of the machines that 
run it probably really cannot upgrade.

For exactly the same reason you mention:

	"Users who need vintage features can use vintage kernels."

ie you end up having people who have vintage hardware, and they use 
vintage kernels, but in their case, the "vintage" is Win95 or Win98. That 
does't mean that the _linux_ machine they use is necessarily vintage.

		Linus

  parent reply	other threads:[~2006-05-12 16:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605110717.k4B7HuVW006999@shell0.pdx.osdl.net>
2006-05-11 17:51 ` + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree Dave Jones
2006-05-12 15:03   ` Jan Engelhardt
2006-05-12 16:19     ` John Kelly
2006-05-12 16:24       ` Steven Rostedt
2006-05-12 16:31         ` John Kelly
2006-05-12 16:40           ` Tom Rini
2006-05-12 16:48             ` Steven Rostedt
2006-05-12 16:52             ` John Kelly
2006-05-12 16:41           ` Steven Rostedt
2006-05-12 16:59           ` Linus Torvalds [this message]
2006-05-12 17:10             ` John Kelly
2006-05-12 17:23               ` Linus Torvalds
2006-05-12 18:13             ` Jeff V. Merkey
2006-05-14  3:11             ` Andrew Morton
2006-05-14  4:37               ` Dave Jones
2006-05-12 17:42           ` Jan Engelhardt
2006-05-12 19:50             ` Jeff V. Merkey
2006-05-12 16:36       ` grundig
2006-05-15 10:01         ` Helge Hafting
2006-05-11 18:12 ` Jesper Juhl
2006-05-11 18:27   ` Andrew Morton
2006-05-11 18:57     ` John Kelly

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=Pine.LNX.4.64.0605120949060.3866@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=jak@isp2dial.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).