From: Andrew Ebling <kernelhacker@lineone.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: pavel@md5.ca, linux-kernel@vger.kernel.org
Subject: Re: kernel changes
Date: 29 Sep 2001 14:43:12 +0100 [thread overview]
Message-ID: <1001770994.404.35.camel@kernighan> (raw)
In-Reply-To: <E15n5lw-0008VS-00@the-village.bc.nu>
In-Reply-To: <E15n5lw-0008VS-00@the-village.bc.nu>
On Fri, 2001-09-28 at 23:06, Alan Cox wrote:
> > been radically changed for "better". Now I don't trust 2.4 line
> > kernel to work *at all*, so cautiously keep all old kernels in the /boot,
> > when upgrading.
> > It seems I am not only one and wonder if something will be done about that.
>
> You certainly aren't the only one. 2.4.10 both really alarms me and doesn't
> survive over night on my test box.
It would be better to be premature starting 2.5.x than to risk damaging
the reputation of Linux by pretending an unproven kernel is stable.
Lets start 2.5.x and let Alan sort 2.4.x out.
Andrew
next prev parent reply other threads:[~2001-09-29 13:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 21:32 kernel changes Pavel Zaitsev
2001-09-28 22:04 ` Mark Frazer
2001-09-28 22:31 ` Ben Greear
2001-09-28 22:33 ` Alan Cox
2001-10-01 9:07 ` Paul Larson
2001-09-28 22:06 ` Alan Cox
2001-09-29 13:43 ` Andrew Ebling [this message]
2001-09-29 7:25 ` Mika Liljeberg
2001-09-29 10:19 ` Ville Herva
2001-09-29 16:45 ` John Alvord
2001-09-29 17:23 ` arjan
2001-09-30 8:17 ` John Alvord
2001-10-01 17:07 ` Martin J. Bligh
[not found] <fa.b97kd6v.8j2vhi@ifi.uio.no>
[not found] ` <fa.hmvo4bv.l2gsaj@ifi.uio.no>
2001-09-29 7:29 ` Dan Maas
2001-10-04 0:36 ` bill davidsen
2001-10-04 9:43 ` John Alvord
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=1001770994.404.35.camel@kernighan \
--to=kernelhacker@lineone.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@md5.ca \
/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