linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Sam Rogers <srogers@redshift.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2 Volume and Volume group naming nomenclature
Date: Mon, 20 Jun 2005 09:34:21 -0700	[thread overview]
Message-ID: <42B6F00D.3060801@redshift.com> (raw)


Ok, I am not try to start a flame war here, but I run dab smack into a 
walk that shouldn't be there. I have managed HPUX for many years which 
is the inspiration for Linux's LVM, and yes I know H.P. did not invent 
LVM. And for the most part you guys have done a pretty good job. I know 
it is a lot of hard work that has gone into this software.

But there is a major problem. LVM2 will not (from what I can see) 
recognize volume group names like VG00. I do not understand? Why type 
Volgroup00 when VG00 is quicker. In the HPUX version you can name the 
volume group and logical volume anything you want. I don't see why we 
can't do the same. It took me over a year to figure why LVM2 was not 
working in an install until I gave up naming the volume group and let it 
default to Volgroup00.

I commend all the programmers for this project, but respectfully ask 
that you change/modify and or add the logical and volume naming feature 
to this great product.

Regards,

    Sam Rogers.

P.S.
   If this is already in development then please disregard this message.

             reply	other threads:[~2005-06-20 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 16:34 Sam Rogers [this message]
2005-06-20 16:49 ` [linux-lvm] LVM2 Volume and Volume group naming nomenclature Jason L Tibbitts III
2005-06-20 16:52   ` gwood
2005-06-22  1:17   ` Michael Gurski
2005-06-22  1:57 ` Olivier Eymere
2005-06-22 10:10 ` Luca Berra
  -- strict thread matches above, loose matches on Subject: below --
2005-06-20 16:30 Sam Rogers

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=42B6F00D.3060801@redshift.com \
    --to=srogers@redshift.com \
    --cc=linux-lvm@redhat.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).