From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] configuration question
Date: Mon, 29 Jan 2001 15:44:57 +0000 [thread overview]
Message-ID: <20010129154457.E8567@srv.sistina.com> (raw)
In-Reply-To: <20010129135716.B511@tykepenguin.com>; from caulfield@sistina.com on Mon, Jan 29, 2001 at 01:57:16PM +0000
On Mon, Jan 29, 2001 at 01:57:16PM +0000, Patrick Caulfield wrote:
> On Fri, Jan 26, 2001 at 08:42:42PM -0600, Steven Lembark wrote:
> >
> > trying to get vg's out of dev for now -- devfs issues.
> >
> > so i modify ./kernel/lvm.h replacing:
> >
> > #define LVM_DIR_PREFIX "/dev/"
> >
> > with
> > #define LVM_DIR_PREFIX "/lvm/"
> >
> > then configure and compile the code.
> >
> > probem is that this doesn't seem to purge /dev/ from
> > all of the code. is there some other location where
> > the lvm directory is defined or is this just a
> > configuration bug [perhaps a known one at that]?
>
> It looks like there are few hardcoded /dev strings elsewhere
> in the code. try a grep down the lib directory and change
> those too. I'll fix this in CVS.
The only one I still found was in tools/lib/pv_check_name.c.
Fixed that and checked it in.
The real constraint here is, that LVM stores the full pathname in the VGDA
and that there's no tool available today to change that information on the fly.
I implemented LVM_DIR_PREFIX a while ago as a helper to ease namespace
changes. But for sure there's still something to do (as it always will ;-)
>
> patrick
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-01-29 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 2:42 [linux-lvm] configuration question Steven Lembark
2001-01-29 13:57 ` Patrick Caulfield
2001-01-29 15:44 ` Heinz J. Mauelshagen [this message]
2001-01-29 15:12 ` Steven Lembark
2001-01-29 16:55 ` Heinz J. Mauelshagen
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=20010129154457.E8567@srv.sistina.com \
--to=mauelshagen@sistina.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).