From: svetljo <galia@st-peter.stw.uni-erlangen.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Lock Patch
Date: Sat, 15 Sep 2001 00:12:38 +0200 [thread overview]
Message-ID: <3BA280D6.5020604@st-peter.stw.uni-erlangen.de> (raw)
In-Reply-To: NBBBJHKIOKPKOGOEPEDPCEFKDNAA.stuart@bh90210.net
i've forgoten
> you saying that typing, "make" in the "PATCHES" directory will cause a patch to be generated specifically for my kernel?
>
thats actually the work of ./configure it trys to find out what you
have, and what you need
in PATCHES it chooses from all the patches the ones your kernel need ,
and " make " put them together in one patch for your kernel
> What name will it be given?
> The documentation says to add a dash dash kernel-dir= or something or other after the "./configure" command, are you saying it is better to use "./configure" absent that appended statement?
> Where do I untar the LVM source? Does it matter where I do so? May I do it in /tmp?
>
1
next prev parent reply other threads:[~2001-09-14 22:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 6:00 [linux-lvm] Lock Patch IT3 Stuart B. Tener, USNR-R
2001-09-14 8:55 ` Patrick Caulfield
2001-09-14 11:10 ` IT3 Stuart B. Tener, USNR-R
2001-09-14 11:41 ` Heinz J . Mauelshagen
2001-09-14 11:55 ` svetljo
2001-09-14 16:28 ` IT3 Stuart B. Tener, USNR-R
2001-09-14 18:17 ` svetljo
2001-09-14 21:21 ` IT3 Stuart B. Tener, USNR-R
2001-09-14 22:05 ` svetljo
2001-09-15 0:27 ` IT3 Stuart B. Tener, USNR-R
2001-09-14 22:12 ` svetljo [this message]
2001-09-15 0:27 ` IT3 Stuart B. Tener, USNR-R
2001-09-15 2:06 ` svetljo
2001-09-14 16:25 ` IT3 Stuart B. Tener, USNR-R
2001-09-14 13:51 ` Chris Mason
2001-09-14 16:32 ` IT3 Stuart B. Tener, USNR-R
-- strict thread matches above, loose matches on Subject: below --
2001-10-11 16:43 [linux-lvm] Lock patch
2001-10-11 17:20 ` Chris Mason
2001-10-12 7:33 ` Patrick Caulfield
2001-10-12 13:44 ` Julian Einwag
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=3BA280D6.5020604@st-peter.stw.uni-erlangen.de \
--to=galia@st-peter.stw.uni-erlangen.de \
--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