mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Joshua Hudson" <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stability of 2.6.17-rc3?
Date: Wed, 10 May 2006 00:01:25 +0200	[thread overview]
Message-ID: <9a8748490605091501r4bcff8b0q630cbf2fa0e33732@mail.gmail.com> (raw)
In-Reply-To: <bda6d13a0605091340x2e16342v15733b2c9612d985@mail.gmail.com>

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

  reply	other threads:[~2006-05-09 22:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 20:40 Joshua Hudson
2006-05-09 22:01 ` Jesper Juhl [this message]
2006-05-10  7:34   ` Jan Engelhardt
2006-05-10  9:41     ` Alistair John Strachan
2006-05-10 22:23       ` Jan Engelhardt
2006-05-11  0:19         ` Alistair John Strachan
2006-05-11 11:23           ` Jan Engelhardt
2006-05-10  7:31 ` Jan Engelhardt

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=9a8748490605091501r4bcff8b0q630cbf2fa0e33732@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=joshudson@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®