From: Erik Andersen <andersen@codepoet.org>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: c0330 <c0330@yingwa.edu.hk>, linux-kernel@vger.kernel.org
Subject: Re: Future of Kernel tree 2.0 ............
Date: Sat, 13 Jul 2002 18:42:28 -0600 [thread overview]
Message-ID: <20020714004227.GE29007@codepoet.org> (raw)
In-Reply-To: <200207131543.49094.roy@karlsbakk.net>
On Sat Jul 13, 2002 at 03:43:49PM +0200, Roy Sigurd Karlsbakk 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.
> >
> > In nowsdays, there are less less compputers using 2.0. We should push
> > them to upgrade, so I think stop developing 2.0 is better, in my opinion
>
> Is there any reason at all to use 2.0 instead of 2.2?
Size. I recall putting together an mmu-less system running a
2.0.x kernel. For the first rev of the board I had just 1 MB
of ram. Try doing that with 2.4.x.... doesn't work.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-07-14 0:39 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 [this message]
2002-07-13 14:53 ` Alan Cox
2002-07-13 15:34 ` Stephen Frost
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=20020714004227.GE29007@codepoet.org \
--to=andersen@codepoet.org \
--cc=c0330@yingwa.edu.hk \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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