From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: linux-kernel@vger.kernel.org
Subject: 2.4.0 quality [was: 2.4.0 uptime]
Date: Fri, 26 Jan 2001 18:47:13 +0200 [thread overview]
Message-ID: <20010126184713.B1002@niksula.cs.hut.fi> (raw)
In-Reply-To: <001601c0876a$db8b5a80$51a81aac@arrowhead.se>
In-Reply-To: <001601c0876a$db8b5a80$51a81aac@arrowhead.se>; from hes@arrowhead.se on Fri, Jan 26, 2001 at 08:37:38AM +0100
On Fri, Jan 26, 2001 at 08:37:38AM +0100, you [Hans Eric Sandström] claimed:
> BP6/Dual Cel 400 (the 2.0 load is setiathome)
> --
> [root@zekeserv /root]# uptime
> 8:28am up 20 days, 13:04, 2 users, load average: 2.00, 2.00, 2.00
> [root@zekeserv /root]# uname -a
> Linux zekeserv 2.4.0 #2 SMP Fri Jan 5 07:37:01 CET 2001 i686 unknown
> [root@zekeserv /root]#
Yeah. I think it can be concluded that 2.4.0 was pretty good for a .0
release. IMHO and based on my own limited experience it's much better than
2.2.0. It certainly does pretty well with that kind of ordinary CPU load,
and the bugs (if any) are related to more exotic conditions.
For most people, it appears to have worked _well_. It certainly has worked
fine for me (I had one X lock up with it, but I'd blame the nvidia drivers
for that altough they are very stable on 2.2.).
What known bugs are there btw? I think the only more serious were the
software RAID5 bug and the VIA driver issues, both of which caused fs
corruption. Some people reported problems with X (is this the same forking
problem Jeff Merkey et all tried to hunt down pre-time), and some had
trouble with booting 386 and/or other hardware. Any more?
Hopefully Linux will squash all of them in 2.4.1!
-- v --
v@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-26 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 7:37 2.4.0 uptime Hans Eric Sandström
2001-01-26 16:47 ` Ville Herva [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=20010126184713.B1002@niksula.cs.hut.fi \
--to=vherva@mail.niksula.cs.hut.fi \
--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®