From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Colin Paul Adams <colin@colina.demon.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: The 2.6 kernel, expected to be released by late next month
Date: 06 May 2003 13:53:52 +0100 [thread overview]
Message-ID: <1052225630.1201.9.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <ltllxk43m6.fsf@colina.demon.co.uk>
On Maw, 2003-05-06 at 14:16, Colin Paul Adams wrote:
> >>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> Alan> Wildly improbable. 2.6-test maybe, but there are way too
> Alan> many bugs left including data corruption.
>
> What sort of data corruption?
>
> I've just ordered a dual Xeon machine, so I was planning to run 2.5.x
> on it, to maximize throughput, but this sounds worrying. perhaps I'd
> better stick to 2.4.n?
At least as of 2.5.68 floppy corrupts data, and there have been odd (but
not horrifying) problems with IDE that Bart may now have fixed. After
that its a case of going through the noise, figuring out which other
minor corruption reports come from the tty bug, vm races, user error,
bad ram and so on.
I run 2.5.x continually on some non critical boxes. I do have backups
but even on 2.4 nothing says my disk wont suddenely fail anyway.
A lot of these are corner cases, and crossing off items one at a time,
not "it eats lots of computers"
prev parent reply other threads:[~2003-05-06 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 7:19 Gabe Foobar
2003-05-06 11:33 ` Alan Cox
2003-05-06 13:16 ` Colin Paul Adams
2003-05-06 12:53 ` Alan Cox [this message]
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=1052225630.1201.9.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=colin@colina.demon.co.uk \
--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®