linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>,
	Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] libdevmapper's handling of devices with spaces in	the name
Date: Wed, 26 Feb 2014 23:26:48 +0000	[thread overview]
Message-ID: <20140226232648.GA6021@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <530E67E9.9060005@ubuntu.com>

On Wed, Feb 26, 2014 at 05:17:13PM -0500, Phillip Susi wrote:
> I'm also still wondering why udev can't simply handle quoted names
> with spaces in them.  People have been dealing with this sort of thing
> in shell for years...
 
Once you've had exposure to udev you soon learn that "wondering why" gets
you nowhere:)  However bizarre, your only option is to conform.
Name mangling in lvm2/device-mapper was designed both to conform and
to still allow for all possibilities in as transparent a way as we could.

The primary new limitation is a reduction in the effective maximum length
of a device name due to the quoting.  If this becomes a problem we will have
to extend the kernal API to support longer names.

Alasdair

  reply	other threads:[~2014-02-26 23:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 17:04 [linux-lvm] libdevmapper's handling of devices with spaces in the name Phillip Susi
2014-02-26 18:21 ` Zdenek Kabelac
2014-02-26 18:37   ` Phillip Susi
2014-02-26 19:12     ` Zdenek Kabelac
2014-02-26 20:52       ` Phillip Susi
2014-02-26 21:40         ` Zdenek Kabelac
2014-02-26 22:17           ` Phillip Susi
2014-02-26 23:26             ` Alasdair G Kergon [this message]
2014-02-27  8:51             ` Peter Rajnoha
2014-02-27  9:08             ` Peter Rajnoha

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=20140226232648.GA6021@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=psusi@ubuntu.com \
    --cc=zkabelac@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).