From: Heinz Mauelshagen <heinzm@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Re: dm targets with spaces in the name
Date: Mon, 15 Dec 2008 15:09:23 +0100 [thread overview]
Message-ID: <1229350163.31942.6.camel@o> (raw)
In-Reply-To: <493D8430.3010904@cfl.rr.com>
Am Montag, den 08.12.2008, 15:31 -0500 schrieb Phillip Susi:
> Alasdair G Kergon wrote:
> > which is a bug as per what I stated above, if true.
> >
> > dmsetup knows nothing about the format of the table line - it's a simple
> > string - and should not be interfering with it: a backslash+space (after any
> > shell escaping) should get handled consistently, passed through to the target
> > and should work.
>
> Nevermind, I must have made a typeo before because now the kernel
> accepts targets with spaces in the name just fine, as long as they are
> properly backslash escaped.
>
> Heinz, you mentioned that dmraid should just not be using names with
> spaces in them. My first thought was to fix dmraid to backslash escape
> the spaces, but you seem to have another idea in mind?
We don't support them in dmraid and I find them principally bogus.
Why not use '_' instead to avoid parsing hassles ?
Heinz
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2008-12-15 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 17:03 dm targets with spaces in the name Phillip Susi
2008-12-04 15:52 ` Heinz Mauelshagen
2008-12-04 20:15 ` Phillip Susi
2008-12-05 1:59 ` Alasdair G Kergon
2008-12-05 16:58 ` Phillip Susi
2008-12-05 17:08 ` Alasdair G Kergon
2008-12-08 20:31 ` Phillip Susi
2008-12-15 14:09 ` Heinz Mauelshagen [this message]
2008-12-15 16:18 ` Phillip Susi
2008-12-16 8:55 ` Heinz Mauelshagen
2008-12-09 13:58 ` Arvin Schnell
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=1229350163.31942.6.camel@o \
--to=heinzm@redhat.com \
--cc=dm-devel@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.