From: Miquel Colom Piza <m.colom@barcelo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5 VM
Date: Fri, 01 Jun 2001 19:15:59 +0200 [thread overview]
Message-ID: <3B17CDCF.AABA522B@barcelo.com> (raw)
This is my first email to the list. I'm not subscribed but I've read it
for years.
I don't agree with those claiming that 2.4.xx is bad or still beta.
We the administrators have the responsability to test early kernels and
send good bug reports so the developers can solve the bugs. That's the
way we can contribute to the community.
But it's really risky to use these kernels on MAIN 24x7 production
servers.
This has been true for 1.2.x 2.0.x (I think that was the best linux
kernel series) 2.2.x and 2.4.x and will be for 2.6.x also
Given we know that the support from open source developers is clearly
better than commercial contract supports, I don't see the reason to
complain about the work of those wonderfull hackers spending their spare
time coding for all of us.
(I'm not subscribed to the list, Please CC me).
next reply other threads:[~2001-06-01 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 17:15 Miquel Colom Piza [this message]
2001-06-01 17:53 ` 2.4.5 VM Ken Brownfield
-- strict thread matches above, loose matches on Subject: below --
2001-06-05 11:18 Martin.Knoblauch
2001-06-05 17:20 ` Alan Cox
2001-06-06 7:06 ` Martin.Knoblauch
2001-06-06 7:42 ` Christian Bornträger
2001-06-06 7:51 ` Alan Cox
2001-06-06 7:45 ` Jonathan Morton
[not found] <Pine.LNX.4.10.10106011028150.6653-100000@webman.medikredit.co.>
2001-06-01 9:27 ` Marcin Kowalski
2001-06-01 14:42 ` Marcelo Tosatti
2001-05-31 22:46 Trever L. Adams
2001-05-31 22:49 ` Alan Cox
2001-05-31 22:56 ` Trever L. Adams
2001-05-31 22:57 ` Alan Cox
2001-06-01 4:27 ` Billy Harvey
2001-06-01 8:29 ` Marcin Kowalski
2001-06-01 8:43 ` David Rees
2001-06-01 15:48 ` Russell Leighton
2001-05-31 22:59 ` Christopher Zimmerman
2001-05-31 23:40 ` Trever L. Adams
2001-05-31 23:56 ` Christopher Zimmerman
2001-05-31 23:58 ` Christopher Zimmerman
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=3B17CDCF.AABA522B@barcelo.com \
--to=m.colom@barcelo.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