From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgscan won't recognize my VG
Date: Tue, 20 Mar 2001 13:21:27 -0700 (MST) [thread overview]
Message-ID: <200103202021.f2KKLR902727@webber.adilger.int> (raw)
In-Reply-To: <3AB7B6EF.AFA0AD4C@in.tum.de> from David Vidal Rodriguez at "Mar 20, 2001 09:00:47 pm"
David Vidal R. (vidalrod@in.tum.de) writes:
> Andreas Dilger wrote:
> > Patch below. Only needed if you have < beta6 kernel code. It probably
> > should be put into the standard tools, however, because a lot of people
> > are still using beta2 kernel code.
>
> err... is this a patch for generating the kernel patch?
No, the patch is for the user tools only. You need to use this patch if
you are using beta6 user tools, but have an older kernel version.
> I _do_ have the beta6 sources, compiled the tools and generated the patch,
> but the kernel doesn't compile. It says sth. about unresolved symbols.
> Indeed, if I compile lvm as a module (lvm-mod.o), I can build the kernel
> and the modules, but there seems to be "unresolved symbols".
What symbols are missing? I assume you applied the resulting kernel patch
to the kernel source tree, and are compiling the LVM module there?
> Hmmm... and I have had to deactivate lines 333-335 in tools/lib/liblvm.h
> because there is a name conflict with this function and the standard one...
Yes, this is OK. Basename has always been a problem.
> I also have had to add the include dir of the kernel source tree to the
> CFLAGS because of a couple of ENOENTs... I have to say that I don't and
> can't have the source tree in the standard location (/usr/src) because
> I'm not root....
???? If you are not root, then how do you expect to install a new kernel
or run the LVM user tools????
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-20 20:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 20:13 [linux-lvm] vgscan won't recognize my VG David Vidal Rodriguez
2001-03-19 20:37 ` Andreas Dilger
2001-03-20 18:52 ` David Vidal Rodriguez
2001-03-20 19:17 ` AJ Lewis
2001-03-20 19:25 ` Andreas Dilger
2001-03-20 19:35 ` David Vidal Rodriguez
2001-03-20 20:00 ` David Vidal Rodriguez
2001-03-20 20:21 ` Andreas Dilger [this message]
2001-03-20 20:36 ` David Vidal Rodriguez
2001-03-21 0:29 ` Kirth
2001-03-21 18:30 ` David Vidal Rodriguez
2001-03-21 19:17 ` Andreas Dilger
2001-03-23 14:55 ` David Vidal Rodriguez
2001-03-23 22:36 ` Andreas Dilger
2001-03-20 20:57 ` [linux-lvm] LVM and fault tolerance Anders Widman
2001-03-21 17:33 ` Lars Kellogg-Stedman
2001-03-22 23:59 ` Anders Widman
[not found] ` <0103262137020G.01456@lyta>
2001-03-27 21:48 ` Anders Widman
2001-03-27 21:56 ` Ragnar Kjørstad
2001-03-27 22:29 ` Anders Widman
2001-03-27 22:45 ` Ragnar Kjørstad
2001-03-28 6:43 ` Russell Coker
2001-03-31 17:17 ` Anders Widman
2001-03-20 20:23 ` [linux-lvm] vgscan won't recognize my VG José Luis Domingo López
2001-03-20 19:31 ` 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=200103202021.f2KKLR902727@webber.adilger.int \
--to=adilger@turbolinux.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).