Messages in this thread | | | Date | Wed, 10 May 2006 00:01:25 +0200 | From | "Jesper Juhl" <> | Subject | Re: Stability of 2.6.17-rc3? |
| |
On 5/9/06, Joshua Hudson <joshudson@gmail.com> wrote: > Was hoping 2.6.17 would be out within one week, doesn't look like it > is going to happen.
It'll be released when it is ready, not according to a fixed schedule... and yes, within one week looks unlikely.
> My thesis defense is coming up, need to merge my patches against some kernel > (requiring 2.6.16.1 looks weird). > > On a machine that 2.6.16.1 runs bug-free, is it sane to assume > 2.6.17-rc3 will as well?
I'd say no.
2.6.17-rc3 is a development kernel, no guarantees about anything really.
If you want a newer kernel stable kernel, then your safest bet would be the latest -stable one, currently that would be 2.6.16.15
> If it fails outright, I can revert, but if it is unstable I'm going to > have some problems.
Development kernels are run completely at your own risk. It may run fine, it may explode at boot, it may cause slow silent corruption, it may eat your lunch, it may cause an alien invasion - all bets are off... (although it actually seems to be getting pretty good, I've been running 2.6.17-rc3-git12 without problems for a while).
> (You would be surprised how long it took me to discover a mistake that > sys_rename(on any filesystem) -> deadlock with my custom patch).
-- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - 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/
| |