From: Mario Vanoni <vanonim@bluewin.ch>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.29-rc1
Date: Sat, 08 Jan 2005 21:39:13 +0100 [thread overview]
Message-ID: <41E044F1.1090802@bluewin.ch> (raw)
Seems the best of all 2.4.# kernels, congrats!
On 7 machines works perfectly,
and on our production,
SMP dual Xeon-2800HT it seems to be a bit faster.
On each machine different NIC's (eth 100Mbits/s),
doing backups every 20 minutes/etc., all 100% perfect.
Not in LKML, cc if you need/want.
Sincere congrats to Marcelo and to all the programmers.
Mario Vanoni, Switzerland Linux user
PS Using Schilling's cdrtools, with his SCSI problems,
I don't think to switch to 2.6.# kernels,
all works perfectly now, time is money,
and I have _ZERO_ time to experiment.
next reply other threads:[~2005-01-08 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 20:39 Mario Vanoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 10:49 Linux 2.4.29-rc1 Marcelo Tosatti
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=41E044F1.1090802@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).