From: Ulrich Wiederhold <U.Wiederhold@gmx.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm-1.0.1-rc4 and 2.4.13
Date: Fri Oct 26 14:27:02 2001 [thread overview]
Message-ID: <20011026213005.C928@sky.net> (raw)
In-Reply-To: <20011026095641.C587@tykepenguin.com>
* Patrick Caulfield <caulfield@sistina.com> [011026 10:56]:
> On Fri, Oct 26, 2001 at 12:54:05AM +0200, Ulrich Wiederhold wrote:
> > Hello,
> > I untared 2.4.13, applied the official xfs patch, then the fresh created
> > lvm patch.
> >
> > No mistakes.
>
> The XFS patch removes some essential LVM bits from the Makefile I think (maybe
> it has an old LVM in there or something)
>
> Edit drivers/md/Makefile and change the lvm-mod-objs line to read:
>
> lvm-mod-objs := lvm.o lvm-snap.o lvm-fs.o
>
Hello,
thanks again.
I did:
* untar the kernel 2.4.13
* patched with xfs
* created lvm-patch
* patched with lvm
* changed the line as described above
* configured the kernel
* built the kernel
This won´t work in another order, e.g. built the lvmpatch with a
vanilla-kernel or apply the lvm patch first! I always got errors doing
this.
Two questions:
1. Why isn´t lvm-1.0.1-rc4 in the current Linux-Kernel? Why do I still
need to patch? I think this version is already stable and better than
the older one, isn´t it?
2. Should I write a bug-report to the xfs-guys? If yes, can I include
your Email, Patrick?
Regards
Uli
--
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5
next prev parent reply other threads:[~2001-10-26 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 17:52 [linux-lvm] lvm-1.0.1-rc4 and 2.4.13 Ulrich Wiederhold
2001-10-26 3:59 ` Patrick Caulfield
2001-10-26 14:27 ` Ulrich Wiederhold [this message]
2001-10-29 2:59 ` Patrick Caulfield
2001-10-29 4:05 ` Ulrich Wiederhold
2001-10-29 4:52 ` GCS
2001-11-03 4:21 ` Paul Dickson
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=20011026213005.C928@sky.net \
--to=u.wiederhold@gmx.net \
--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.