linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: "Stuart D. Gathman" <stuart@bmsi.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Inconsistent naming...?
Date: Wed, 13 Jul 2011 17:11:41 +0100	[thread overview]
Message-ID: <20110713161141.GX7857@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1107131137130.28748@bmsred.bmsi.com>

On Wed, Jul 13, 2011 at 11:39:48AM -0400, Stuart D. Gathman wrote:
> I apologize for not being more helpful and actually posting such a script
> (would be happy to do so when I find the link to the quoting spec),
> but I would write a python script (or even a C program in the unlikely event
> it becomes a bottleneck) to quote/unquote lv names.  Use that
> in your shell scripts to get the dev name.

Oh - you've just reminded me:
  dmsetup splitname

Alasdair

  reply	other threads:[~2011-07-13 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11  1:31 [linux-lvm] Inconsistent naming...? Linda A. Walsh
2011-07-11  2:16 ` Alasdair G Kergon
2011-07-11  2:27   ` Linda A. Walsh
2011-07-18  5:52   ` Luca Berra
     [not found]     ` <4E2538E1.9040806@tlinx.org>
2011-07-19 15:39       ` [linux-lvm] mount's (&udev's) dirty little naming problem -- (was Inconsistent naming...?) Luca Berra
2011-07-11  2:58 ` [linux-lvm] Inconsistent naming...? Alasdair G Kergon
2011-07-13 10:47   ` Linda A. Walsh
2011-07-13 15:39     ` Stuart D. Gathman
2011-07-13 16:11       ` Alasdair G Kergon [this message]
2011-07-13 17:34         ` Males, Jess
2011-07-13 18:47           ` Alasdair G Kergon
2011-07-14  4:05             ` Linda A. Walsh
2011-07-18  2:38     ` [linux-lvm] Inconsistent naming needs to be fixed (was Re: Inconsistent naming...?) Linda A. Walsh

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=20110713161141.GX7857@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=stuart@bmsi.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).