All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Snyder <ben@jumpline.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] enterprise kernel
Date: Tue Nov  5 11:27:02 2002	[thread overview]
Message-ID: <3DC7FF36.3000504@jumpline.com> (raw)

My company uses a software package that 'requires' a RedHat Enterprise 
kernel.  The word 'requires' is in quotes as it doesnt seem to be 
required other than by the vendor's policy.  They wont support it if 
it's not enterprise, although the software seems to function just fine.

The problem I'm running into, is that LVM doesnt seem to be included in 
the enterprise build available from RedHat in rpm format.    I know I 
can build my own enterprise kernel, but I'm an RPM rookie (in the 
context of creating them).

I am curious if anyone out there knew of a workaround or a pre-existing 
config file that I can plug into my kernel source or rpm spec file that 
will provide the compile options and/or modules for LVM to function 
correctly in a 2.4 enterprise kernel?  The whole idea of kernels in 
pre-configured in rpm format makes me shudder, but I have to do what I 
have to do in order to get things working.

aTdHvAaNnKcSe

                 reply	other threads:[~2002-11-05 11:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3DC7FF36.3000504@jumpline.com \
    --to=ben@jumpline.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 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.