From: "Dale Gallagher" <foobar@mighty.co.za>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Compile problem - Linux 2.6.1 + LVM2.2.00.08
Date: Mon Jan 19 09:33:01 2004 [thread overview]
Message-ID: <web-210831654@mail01.infosat.net> (raw)
In-Reply-To: <20040119115243.GD5542@percy.comedia.it>
> compile and install device mapper first
Tried that earlier and it failed too - after reading the
docs, wasn't certain if I had to do this, since 2.6.x has
device-mapper in the kernel....
Anyway, everything succeeded now - the problem was with my
kernel-headers. I'd been a twit and symlinked
/usr/include/linux to
/usr/src/linux-2.6.1/usr/include/linux and found Linus'
post regarding this, before rectifying my mistake:
http://www.ussg.iu.edu/hypermail/linux/kernel/0007.3/0587.html
So I removed my symlink madness and re-installed the
original kernel-headers package as per my original post and
then successfully installed both device-mapper and LVM!
Thanks
Dale
prev parent reply other threads:[~2004-01-19 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 6:20 [linux-lvm] Compile problem - Linux 2.6.1 + LVM2.2.00.08 Dale Gallagher
2004-01-19 6:54 ` Luca Berra
2004-01-19 9:33 ` Dale Gallagher [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=web-210831654@mail01.infosat.net \
--to=foobar@mighty.co.za \
--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