From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] 2.2.19 Patches??
Date: Sun, 8 Apr 2001 22:40:43 -0500 [thread overview]
Message-ID: <20010408224043.A19238@sistina.com> (raw)
In-Reply-To: <3ACFA28B.AE154AE5@ednet.ns.ca>; from boutilpj@ednet.ns.ca on Sat, Apr 07, 2001 at 08:28:11PM -0300
[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]
On Sat, Apr 07, 2001 at 08:28:11PM -0300, Patrick Boutilier wrote:
> I didn't see that option either but the LVM information is in /proc so it must be
> in by default now.
Precisely right. If you look at LVM/kernel/lvm.c, you'll see that this was
changed on Jan. 8, 2001. (search for 08/01/2001)
> 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
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
AJ Lewis
Sistina Software Inc. Voice: 612-379-3951
1313 5th St SE, Suite 111 Fax: 612-379-3952
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
(Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
-----Begin Obligatory Humorous Quote----------------------------------------
cthread. cthread_fork(). Fork, thread, fork!
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-04-09 3:40 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
2001-04-09 3:40 ` AJ Lewis [this message]
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=20010408224043.A19238@sistina.com \
--to=lewis@sistina.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;
as well as URLs for NNTP newsgroup(s).