Linux LVM users
 help / color / mirror / Atom feed
From: Devin Broce <randomx@storix.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Re: linux-lvm digest, Vol 1 #291 - 15 msgs
Date: Fri, 17 Aug 2001 13:24:26 -0700	[thread overview]
Message-ID: <3B7D7D7A.9F1B6FC2@storix.com> (raw)
In-Reply-To: 200108161601.tno9lh.ijc.37kbpol@augustus

> Gerry,

I messed with patching RedHat's 7.1 kernel for few days before I just went out and
got the latest stable clean source from kernel.org.  Patched, compiled and installed  the first time out.  Much nicer all
around...

Devin

>
>
> > Hello!!
> >          I am trying to get lvm working on redhat 7.1 with kernel
> > 2.4.2-2. I down loaded the source rpm's 1)
> > lvm-iop-0.9.1_beta6-1.src.rpm   2)
> > lvm-iop-patchgen-0.9.1_beta6-1.src.rpm  and the base rpm 3)
> > lvm-base-1.1-1.i386.rpm. I did a rpm --rebuild and ran the rpm command
> > and all seemed to install well with no problems. The problem I did
> > discover is that there is no lvm dir. in /proc and the lvm-mod is
> > nowhere to be found. I was under the impression that kernel 2.4 has lvm
> > already built in. I did a insmod lvm-mod and modprobe lvm-mod and nada.
> > I cannot figure out what I am doing wrong or if I should not be using
> > this version of lvm and use lvm 1.0 instaed (will it work on redhat?).
> > Thanks, Chris.
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> >
>
> Gerry
> --
> "The lyfe so short, the craft so long to learne"  Geoffrey Chaucer
>

       reply	other threads:[~2001-08-17 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200108161601.tno9lh.ijc.37kbpol@augustus>
2001-08-17 20:24 ` Devin Broce [this message]
     [not found] <200108162001.f7GK1r299082@harmonyworks.net>
2001-08-16 20:35 ` [linux-lvm] Re: linux-lvm digest, Vol 1 #291 - 15 msgs Chris Bourne

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=3B7D7D7A.9F1B6FC2@storix.com \
    --to=randomx@storix.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