From: Mario Vanoni <vanonim@bluewin.ch>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: IMHO the usability of 2.6
Date: Sat, 17 Apr 2004 20:53:22 +0200 [thread overview]
Message-ID: <40817D22.2030107@bluewin.ch> (raw)
Tested 2.6.1[-mm#] and 2.6.5[-aa#]:
inexplicables crashes, mouse, NFS etc.,
on 2-3 of our 8 Linux machines (0.1-6 years old),
not usable for production, need five 9 (99.999).
I don't have logs, always switched back to 2.4.25.
Starting with AT&T UNIX SVR2 (1986, rock solid),
later Linux 2.0, then 2.2, then 2.4,
2.4.17 was the 1st veritable stable 2.4 kernel.
2.4.25 had an uptime >=33 days before changing
all machines to 2.4.26. Stable since 1-3 days.
Feedback only and
kind regards
Mario Vanoni, _not_ in lkml!
PS The standalone 9th M$ machine at job,
boot each morning,
some days needs 1-3 reboots on the same day.
From the view point five 9 a piece of jewellery.
next reply other threads:[~2004-04-17 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 18:53 Mario Vanoni [this message]
2004-04-17 19:22 ` IMHO the usability of 2.6 Zwane Mwaikambo
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=40817D22.2030107@bluewin.ch \
--to=vanonim@bluewin.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.