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 - 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/
This archive was generated by hypermail 2b29 : Sun Sep 30 2001 - 21:01:06 EST