From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: ahorn@deorth.org, reiserfs-list@namesys.com
Subject: Re: Status of reiserfs in Redhat 2.4.7-10 kernel ?
Date: 16 Apr 2003 09:17:24 -0400 [thread overview]
Message-ID: <1050499043.10791.137.camel@tiny.suse.com> (raw)
In-Reply-To: <3E9D0744.9090907@namesys.com>
On Wed, 2003-04-16 at 03:33, Hans Reiser wrote:
> I am afraid that I can only say that Redhat kernels are not standard
> kernels, and non-standard kernels should not be preferred for use in
> production systems. They are not as well tested (or as debugged) as
> Linus/Marcelo kernels. Linus/Marcelo kernels are the official kernels,
> and Linus and Marcelo, not RedHat or any other distro, are the Linux
> kernel maintainers. I personally try to avoid any use of a non-standard
> kernel in systems I care about because I know that no distro has the
> testing ability of those who test the Marcelo kernels, and Marcelo's
> level of skill and caution exceeds that of any other maintainer I am
> familiar with in detail, but I am more conservative than most.
Grin, Hans and I have had this debate before, you might want to read
through the reiserfs list archives for all the details. Just look for
the thread where Hubert Mantel most recently posted.
The short version is that I would pick a current vendor kernel over a
current vanilla kernel any day for heavy production use. In terms of
performance and stability the vendor kernel will usually do better. The
kinds of QA done on large hardware and heavy workloads is significantly
better before a vendor release than a vanilla release.
The problem is in defining 'current'. I haven't followed the rhas
releases enough to know if they still qualify.
Anyway there's no need to start that debate again, neither Hans nor I
have changed our minds ;-)
-chris
next prev parent reply other threads:[~2003-04-16 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 23:10 Status of reiserfs in Redhat 2.4.7-10 kernel ? ahorn
2003-04-15 23:35 ` Philippe Gramoullé
2003-04-16 1:07 ` ahorn
2003-04-16 7:31 ` Oleg Drokin
2003-04-16 7:33 ` Hans Reiser
2003-04-16 8:14 ` ahorn
2003-04-16 16:11 ` Valdis.Kletnieks
2003-04-16 13:17 ` Chris Mason [this message]
2003-04-16 15:58 ` Hans Reiser
2003-04-16 19:55 ` Gerrit Hannaert
2003-04-17 15:57 ` Hans Reiser
2003-04-17 16:18 ` Chris Mason
2003-04-16 7:57 ` Anders Widman
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=1050499043.10791.137.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=ahorn@deorth.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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.