Re: 2.6 flavours
Date: Thu Dec 16 2004 - 15:40:46 EST
From: Maciej Soltysiak <solt2@xxxxxxxxxxxxxxxxx>
Date: Thu, Dec 16, 2004 at 09:13:56PM +0100
> AFAICS the -ac tree should be the most stable of all kernels, right?
> -mm is totally bleeding edge
I don't agree there. It is bleeding edge, but Andrew makes a conscious
decision when to release it, and I'm sure part of that decision is
thinking about when things will be stable enough to work for many
> -bk the same
bk is the central repository, and depending on when you pull it, you may
have just catched Linus asleep after merging patch 1, meaning the tree
is unstable until he wakes up and merges patch 2.
There is no conscious 'release moment' - this is totally bleeding edge.
> -ck is experimental
There are 'release moments' here too.
> Others are experimental too.
> Looking at the changelogs, the most reasonable kernel to use for
> generic use are the -ac kernels, which I am going to use since 2.6.10
> as long as Alan is kindly going to continue his fabulous work.
I've understood the 2.6.x-ac kernels started with some ide work, then
included some serial fixes, and may or may not have other bug fixes.
>From what I read, they are not as all-including as the 2.4.x-ac kernels
were. Those I recognize most in the 2.6.x-mm kernels.
> I swear not to use 2.6.10 until Alan publishes 2.6.10-ac1 :-)
Whatever you think best, of course. That may be the release where Alan
says 'Here's the new, experimental next-generation SATA code. It'll
probably break every partition you have. Send me bug-reports' :-)
My way of keeping my home system up is to test a new kernel first on my
laptop (which has good backups and little configuration), then read this
list for some days and then install it on my main workstation (which
also has good backups). Only after some weeks quiet I think about such a
kernel on my firewall/router. Keeping backups helps when testing
I never think, sir. Didn't get a degree.
Chief Inspector Morse
Debian (Unstable) GNU/Linux 2.6.10-rc3 2x6078 bogomips load 0.23
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/