From: Petro <petro@corp.vendio.com>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM 1.0.7
Date: Mon Jun 16 21:25:02 2003 [thread overview]
Message-ID: <20030617021928.GB3614@corp.vendio.com> (raw)
In-Reply-To: <20030617021306.GA22251@www.13thfloor.at>
On Tue, Jun 17, 2003 at 04:13:07AM +0200, Herbert Poetzl wrote:
> On Mon, Jun 16, 2003 at 04:43:58PM -0700, Petro wrote:
> > On Sat, Jun 14, 2003 at 05:37:42AM +0200, Herbert Poetzl wrote:
> > > On Fri, Jun 13, 2003 at 06:25:50PM -0700, Petro wrote:
> > > > When building the 2.4.21 kernel does one still need to apply the patches
> > > > generated by LVM/1.0.7/PATCHES/Makefile?
> > > > I'm having issues with the kernel building and a lot of errors seem to
> > > > be coming from the (patched) LVM stuff.
> > > you could try this patch ...
> > > http://www.13thfloor.at/VServer/patches-2.4.21-c17/07_lvm-1.0.7-2.4.21pre5.patch.bz2
> > > which actually works for me ...
> > The make file halts with a
> > You haven't applied the rawio patch, please see the README
> > make: *** [check_rawio] Error 1
> let me get this straight,
> you download a vanilla 2.4.21 kernel, unpack it, apply
> the patch mentioned above, configure it accordingly and
> start a kernel compile, which then breaks with the message
> given above?
No, sorry--the formatting of the message was really, really bad.
I downloaded the 1.0.7 stuff from Sistina, I downloaded the raw
kernel, then tried to generate the patch myself.
It didn't work, however:
> I do not believe this, I tried it myself, and it compiled
> flawlessly ...
> I guess I am misreading your email?
> > Which is really odd since the README in the PATCHES directory
> > doesn't mention a rawio patch for the 2.4 series.
> which readme?
README, the only README in the patches directory.
> > The 2.4.20-VFS-lock.patch fails against the "raw" (i.e. d/l'd from
> > kernel.org kernel.
> raw = vanilla here?
Yes.
> > The above patch applies and builds "properly" (i.e. compiles w/out
> > failure) against a clean linus kernel.
> the VFS-lock patch or the lvm patch?
Your patch.
--
"On two occasions, I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able to rightly apprehend the kind of confusion
of ideas that could provoke such a question." -- Charles Babbage
prev parent reply other threads:[~2003-06-16 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 20:27 [linux-lvm] LVM 1.0.7 Petro
2003-06-13 22:38 ` Herbert Poetzl
2003-06-16 18:45 ` Petro
2003-06-16 21:13 ` Herbert Poetzl
2003-06-16 21:25 ` Petro [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=20030617021928.GB3614@corp.vendio.com \
--to=petro@corp.vendio.com \
--cc=herbert@13thfloor.at \
--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.