From: "William Blunn" <bill@tao-group.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] To compile
Date: Mon Feb 25 03:13:02 2002 [thread overview]
Message-ID: <001801c1bddc$b32b51e0$216410ac@tao.co.uk> (raw)
In-Reply-To: <wxxzo1yecqu.fsf@nommo.uio.no>
Terje Kvernes <terjekv@math.uio.no> wrote:
> "William Blunn" <bill@tao-group.com> writes:
> > Er, you might find that it is a good idea to put your LVM shared
> > library in /lib.
> >
> > Otherwise you might have difficulting starting up the system if /usr
> > or /usr/local is on an LVM volume.
>
> right. this also goes for vgscan and vgchange. now, site-specific
> software around where I work gets tossed to /site. which of course
> is either a partition or a volume. either way, doing:
>
> [root@host /sbin]# ln -s /site/sbin/vgchange && ln -s /site/sbin/vgscan
>
> isn't as bright as one first thinks.
>
> of course, when testing for volumegroups only / has been mounted, in
> case any other mountpoints are logical volumes. *sigh*
I set up:
/opt/lvm-1.0.1 in the (small) root FS
/usr/local/opt/lvm-1.0.1 in the /usr filesystem (on LVM)
I put the LVM tools at /opt/lvm-1.0.1/sbin, and symlinked them from /sbin.
I put the manpages in /usr/local/opt/lvm-1.0.1/man, and symlinked them
from /usr/local/man.
I put the runtime/shared-object (.so) library directly in /lib.
I put the development/static (.a) library in
/usr/local/opt/lvm-1.0.1/lib, and symlinked it from /usr/local/lib.
After all this, I wondered how difficult it would be to make a
Debian/Potato package out of it.
Bill
next prev parent reply other threads:[~2002-02-25 3:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 6:02 [linux-lvm] To compile Pierrick PONS
2002-02-21 6:45 ` Markus Dobel
2002-02-21 7:03 ` Pierrick PONS
2002-02-21 7:15 ` William Blunn
2002-02-24 16:28 ` Terje Kvernes
2002-02-25 3:13 ` William Blunn [this message]
2002-02-25 7:43 ` [linux-lvm] Problems mounting LVM volume as root Felix Rodriguez
2002-02-26 11:33 ` Luca Berra
2002-02-27 7:30 ` Felix Rodriguez
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='001801c1bddc$b32b51e0$216410ac@tao.co.uk' \
--to=bill@tao-group.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).