From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] 2.2.19 Patches??
Date: Sat, 07 Apr 2001 20:28:11 -0300 [thread overview]
Message-ID: <3ACFA28B.AE154AE5@ednet.ns.ca> (raw)
In-Reply-To: Pine.LNX.4.30.0104071239490.1215-100000@leopard.dorfam.ca
I didn't see that option either but the LVM information is in /proc so it must be
in by default now.
gerry@dorfam.ca wrote:
> Well, I tried to follow the instructions and surprisingly...LVM is working
> with a fresh new 2.2.19 kernel! I found it confusing to install patches
> labeled for other kernels. Also, I don't normally venture into the realm
> of building my own kernel patches!
>
> I had a question though. When I got LVM working with the older 2.2.17
> kernel I had two choices when I was running make xconfig. The first was
> to include LVM as inline or a module and the second was for lvm proc
> support. This time around with the 2.2.19 kernel I didn't get the lvm
> proc support option. Did I miss something???
>
> Gerry
>
> On Fri, 6 Apr 2001, Patrick Boutilier wrote:
>
> > Below is some instructions direct from the README in the PATCHES directory.
> > If you want to get your own raw-io patch get
> > ftp://ftp.kernel.org/pub/linux/kernel/people/sct/raw-io/kiobuf-2.2.18.tar.bz2.
> > I used raw-2.2.18.FULL.diff to patch my 2.2.19 kernel.
> >
> >snip....
> >
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
next prev parent reply other threads:[~2001-04-07 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 23:34 [linux-lvm] 2.2.19 Patches?? gerry
2001-04-07 0:01 ` Goetz Bock
2001-04-07 0:21 ` Patrick Boutilier
2001-04-07 16:46 ` gerry
2001-04-07 23:28 ` Patrick Boutilier [this message]
2001-04-09 3:40 ` AJ Lewis
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=3ACFA28B.AE154AE5@ednet.ns.ca \
--to=boutilpj@ednet.ns.ca \
--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;
as well as URLs for NNTP newsgroup(s).