From: Ben Greear <greearb@candelatech.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel changes
Date: Fri, 28 Sep 2001 15:31:54 -0700 [thread overview]
Message-ID: <3BB4FA5A.C30C1AA6@candelatech.com> (raw)
In-Reply-To: <20010928143205.B3669@md5.ca> <20010928180452.A6093@somanetworks.com>
Mark Frazer wrote:
>
> The answer is to treat all linus/ac/aa/... kernels as development
> kernels. Don't treat anything as stable until it's been through
> a real QA cycle. I've heard Suse, RedHat and the like don't do a
> bad job at this.
I agree, except that the earlier 2.4.0 kernels they are using
are also buggy to one degree or another (for instance, the Tulip
driver didn't start working for my cards untill about 2.4.8, and
by then the VM seems to have gone berserk...) Hell, many of the
official kernels won't even compile with certain options turned
on, which is really frightening, and makes it hard to run regression
tests...
It's almost like we need to fork off a 2.5 kernel just to let the
pressure for massive change off, and let less panic'ed changes go
into the 2.4 series...
The fact that there's a 20MB patch to get from Linus to AC is also
disconcerting!!
Ben
>
> -
> 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/
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-09-28 22:25 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 [this message]
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
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=3BB4FA5A.C30C1AA6@candelatech.com \
--to=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.