Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S314634AbSGMPcp>; Sat, 13 Jul 2002 11:32:45 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S314680AbSGMPcp>; Sat, 13 Jul 2002 11:32:45 -0400
Received: from ns.snowman.net ([63.80.4.34]:8714 "EHLO ns.snowman.net")
	by vger.kernel.org with ESMTP id <S314634AbSGMPco>;
	Sat, 13 Jul 2002 11:32:44 -0400
Date: Sat, 13 Jul 2002 11:34:46 -0400
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 ............
Message-ID: <20020713153446.GZ653@ns>
Mail-Followup-To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	c0330 <c0330@yingwa.edu.hk>, linux-kernel@vger.kernel.org
References: <E17TUXf-0000Ow-00@ited.yingwa.edu.hk> <1026572006.9956.106.camel@irongate.swansea.linux.org.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="QnGs129iAKyuXRcc"
Content-Disposition: inline
In-Reply-To: <1026572006.9956.106.camel@irongate.swansea.linux.org.uk>
User-Agent: Mutt/1.4i
X-Editor: Vim http://www.vim.org/
X-Info: http://www.snowman.net
X-Operating-System: Linux/2.4.18 (i686)
X-Uptime: 11:31:48 up 11 days, 13:57, 10 users,  load average: 1.09, 1.02, 1.01
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1949
Lines: 51


--QnGs129iAKyuXRcc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* 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=20
> > of 2.6?  I think we would put our focus on much more newer kernel. And =
I found=20
> > this may confuse the newbies, because they don't know much about versio=
ning in=20
> > Kernel.
>=20
> 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

--QnGs129iAKyuXRcc
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9MEiVrzgMPqB3kigRAgfAAJ97vwBdePjMYMoMEmh0VImyQhhyBACcCcq7
dnYSoi2qL/kgQ/wklgwBrr0=
=D6nM
-----END PGP SIGNATURE-----

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