All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Kemp <dale@inet.net.nz>
To: Linux LVM mailing list <linux-lvm@msede.com>
Subject: Re: [linux-lvm] LVM /dev and /proc problems and change proposal
Date: Sun, 25 Jun 2000 22:01:30 +1200	[thread overview]
Message-ID: <3955D87A.590E9C2C@inet.net.nz> (raw)
In-Reply-To: 20000625103032.A3124@hmsysv.t-online.de

> But It dissallows the user to do it and there's still plenty of free namespace
> to find a meaningfull name for the Volume Group.

I'm refering to the future when a new device gets added that just might
clash with a volume group name that a user has chosen. And we don't know
what users are going to call their volume groups and we don't know what
device names will be created in the future.

> There's a preprocessor definition LVM_DIR_PREFIX in the code, which
> supports this already.

So I see. The simplest solution is to change this default prefix, and have the
lvm stuff self-contained in its own subdirectory. Even without the name
clash this is just tidier, already /dev is very wide but not very deep.

> I don't like both, because they break the hierarchy of LVs (like virtual
> partitions) contained in VGs (like virtual disks containing physical disks).

Fair enough :-)  Just throwing some ideas around.

Can I `propose' that simply by changing the default (LVM_DIR_PREFIX) in the
original LVM code and we begin `standardizing' now the LVM directories.

eg.

  /dev/lvm/ (all previuos
    |
    +-- lvm [c:109,0] (need to change constant LVM_DIR in "liblvm.h" too]
    |
    +-- vdisk1/
         |
         +-- group [c:109,0]
         +-- lvol1 [b:58,0]
         +-- lvol2 [b:58,1]


> > Also I think there should be a sub-directory for lvm itself in /proc
> > ie. /proc/lvm/lvm instead of /proc/lvm.
>
> Yep.
> Already on the TODO list.
> I share your point of view in regard to /proc.

The need for /proc/lvm/... is simular to that for /dev/lvm/...

-- Dale.

  reply	other threads:[~2000-06-25 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-25  6:35 [linux-lvm] LVM /dev and /proc problems and change proposal Dale Kemp
2000-06-25  8:30 ` Heinz J. Mauelshagen
2000-06-25 10:01   ` Dale Kemp [this message]
2000-06-25 11:16     ` Heinz J. Mauelshagen
2000-06-25 11:35       ` Dale Kemp
     [not found]       ` <3956DF94.218CA65E@inet.net.nz>
2000-06-26  7:13         ` 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=3955D87A.590E9C2C@inet.net.nz \
    --to=dale@inet.net.nz \
    --cc=linux-lvm@msede.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.