public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: c0330 <c0330@yingwa.edu.hk>, linux-kernel@vger.kernel.org
Subject: Re: Future of Kernel tree 2.0 ............
Date: Sat, 13 Jul 2002 11:34:46 -0400	[thread overview]
Message-ID: <20020713153446.GZ653@ns> (raw)
In-Reply-To: <1026572006.9956.106.camel@irongate.swansea.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
> On Sat, 2002-07-13 at 22:35, c0330 wrote:
> >   Will kernel tree 2.0 stop developing and regard historical after the release 
> > of 2.6?  I think we would put our focus on much more newer kernel. And I found 
> > this may confuse the newbies, because they don't know much about versioning in 
> > Kernel.
> 
> Why should you care ? 2.0 can continue to slowly and cautiously get
> critical bug fixes between now and the end of time providing someone
> cares enough to do the work. There are plenty of 2.0 boxes employed as
> routers, print servers, intranet dialins etc which will probably only
> become 2.4 boxes when the hardware is taken out of service.

I tend to agree with you though I did want to mention that I've got
2.4.18 running on my 386 without any problems so far, just because it's
pretty neat that it works so well.  The machine spends a bit more time
in swap I think which makes some things slow down but that could also be
due to bind9 and sendmail being bigger than they used to be (it's my
secondary DNS server and my primary relay server).  Not disagreeing with
you or questioning what you're saying at all, just mentioning my success
with 2.4.18 on a 386 DX/40 w/ 8M of ram.

	Stephen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-07-13 15:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13 21:35 Future of Kernel tree 2.0 c0330
2002-07-13 13:37 ` William Lee Irwin III
2002-07-13 13:41 ` Rik van Riel
2002-07-13 13:43 ` Roy Sigurd Karlsbakk
2002-07-13 16:07   ` Gerhard Mack
2002-07-13 17:11     ` Thunder from the hill
2002-07-14  0:42   ` Erik Andersen
2002-07-13 14:53 ` Alan Cox
2002-07-13 15:34   ` Stephen Frost [this message]
2002-07-13 15:36 ` Jose Luis Domingo Lopez
2002-07-13 16:28 ` Austin Gonyou
2002-07-13 23:49   ` David Weinehall
2002-07-15  4:07     ` Austin Gonyou
2002-07-15 19:22     ` Bill Davidsen
2002-07-15 19:42       ` Jeff Dike
2002-07-13 23:37 ` David Weinehall
2002-07-15  2:16   ` Eric W. Biederman

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=20020713153446.GZ653@ns \
    --to=sfrost@snowman.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=c0330@yingwa.edu.hk \
    --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