From: "Linda A. Walsh" <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Inconsistent naming...?
Date: Wed, 13 Jul 2011 03:47:03 -0700 [thread overview]
Message-ID: <4E1D77A7.4030801@tlinx.org> (raw)
In-Reply-To: <20110711025811.GF7857@agk-dp.fab.redhat.com>
Alasdair G Kergon wrote:
> On Sun, Jul 10, 2011 at 06:31:27PM -0700, Linda A. Walsh wrote:
>
>> Notice the device name. notice how the single dashes are now displayed
>> as two dashes?!?!
>>
>
> Roughly: a dash is the separator we chose, and we double it to escape a
> real dash. But we still need to extend our escaping mechanism to handle
> characters that udev states it doesn't support in primary device names
> but which the old /dev did used to support (and so we still do).
>
----
Roughly, if I give a script the mount point of a logical device, how
can I find
out the name of the LV it is on?
Before I stumbled upon this quote-hack, I could look the mount point in
/proc/mounts and get the dev name.
But since the devname in /proc/mounts is corrupt -- that's not possible.
So what is the recommended way to do something that should be very
simple,
but is not because of a specialized 'quoting' scheme (sigh)...just
tired...I should
be in bed, but was trying to do a snap and fix the scripts...but ug...
Maybe tomorrow...I'll think of someting else, or you have something
to recommend,
since it sounds like you want to change the mangling even more so the
device name won't match what what is in /proc/mounts...
(How can that not be a bug? Does proc/mounts double quote every '-'?
with another?_
Thanks...
linda
next prev parent reply other threads:[~2011-07-13 10:47 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 [this message]
2011-07-13 15:39 ` Stuart D. Gathman
2011-07-13 16:11 ` Alasdair G Kergon
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=4E1D77A7.4030801@tlinx.org \
--to=lvm@tlinx.org \
--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 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.