Linux LVM users
 help / color / mirror / Atom feed
From: Tim <tim@connectlive.com>
To: linux-lvm@sistina.com
Subject: Re: re[2]: [linux-lvm] System Suggestions
Date: Wed Mar  6 17:00:03 2002	[thread overview]
Message-ID: <20020306180032.B12548@connectlive.com> (raw)
In-Reply-To: <1015450169.3240.80.camel@Steven>; from critch@dtsam.com on Wed, Mar 06, 2002 at 03:29:28PM -0600

Whatever other people may say about RedHat, I have found that (with rare
and well-documented exceptions) their kernels (as kernel-2.x.x-source
and kernel-2.x.x-headers RPMs) accept patches fairly well (if not, I'm
comfortable doing it manually) and have been reliable in some extremely
high-load environments, when properly customized.  RH is most definitely
not perfect, but 7.2 is IMHO a perfectly serviceable starting point for
large systems.  I have used Debian, LinuxPPC, Solaris, AIX, FreeBSD,
etc. in the past and they all have their ups and downs, but my *nix
systems are either OpenBSD or RedHat these days, and the reason is
simply that I can get better support for them than anything else.

LVM on RH7.2 has worked well for me, but as I previously mentioned, the
support for LSI Logic boards is quite solid, and using hardware
enclosures eliminates an enormous number of potential problems.


> Although my first thought is to write RH and remind them how much we
> hate it when they build things in a non standard way and therefore cause
> other standard systems to break. I have several peices of hardware that
> are only supported with a RH kernel. I may be braver than some in the
> fact that I have removed the RH kernel and used in to build other
> distros with it. RH should provide a source version of the kernel in
> which you can attempt to put XFS into, then compile, and should still be
> able to load the promise driver into that new kernel. It will take some
> effort, but should be usable. Of course you could return it as
> essentially broken and buy the 3ware card that has better support.

-- 
     "To be suspended from the legal profession is the moral equivalent of 
      being ostracized by child molesters."
                                                           --Ian Rowan

  parent reply	other threads:[~2002-03-06 17:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06 15:04 re[2]: [linux-lvm] System Suggestions Greg Freemyer
2002-03-06 15:11 ` Theo Van Dinter
2002-03-06 15:25   ` Anders Widman
2002-03-06 15:51     ` Anthony W. Marino
2002-03-06 15:46   ` Anthony W. Marino
2002-03-06 15:57     ` Theo Van Dinter
2002-03-06 16:02       ` Anthony W. Marino
2002-03-06 21:40   ` Petro
2002-03-06 21:52     ` Benjamin Scott
2002-03-06 22:47     ` Tim
2002-03-07  4:26       ` Anthony W. Marino
2002-03-07  4:05     ` Anthony W. Marino
2002-03-06 22:15   ` Stuart Levy
2002-03-07  4:24     ` Anthony W. Marino
2002-03-07  9:29     ` Stuart Levy
2002-03-06 15:23 ` re[2]: " Seth Mos
2002-03-06 15:39   ` Anthony W. Marino
2002-03-07  0:32     ` Seth Mos
2002-03-07  4:07       ` Anthony W. Marino
2002-03-07  8:57       ` Tim
2002-03-06 15:30 ` Steven Critchfield
2002-03-06 15:59   ` Kirby C. Bohling
2002-03-06 16:37     ` José Luis Domingo López
2002-03-06 16:41     ` José Luis Domingo López
2002-03-06 17:00   ` Tim [this message]
2002-03-06 15:43 ` re[2]: " Anthony W. Marino
2002-03-06 16:52 ` Tim

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=20020306180032.B12548@connectlive.com \
    --to=tim@connectlive.com \
    --cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox