From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Xen development list <xen-devel@lists.xensource.com>,
Kurt Garloff <garloff@suse.de>
Subject: Re: block-nbd script and example config
Date: Wed, 19 Oct 2005 17:07:05 -0500 [thread overview]
Message-ID: <4356C389.1080804@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E4B9@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>disk = [ 'nbd:134.100.233.115 20004,hda1,w' ]
>
>I think having the space in the export device name is just a little too
>nauseating :-)
>
>Could we make the script take ip:port and then turn the ':' into a space
>when invoking nbdclient?
>
>On this subject, I think it would be less confusing if we configured
>disks using a syntax more akin to that which we use for networking e.g.:
>
>
I actually like this idea a lot. I'm not a huge fan of the current
block device configuration.
>disks = [ 'export=phy:/dev/sda1, target=/dev/sda1, options=rw',
> 'export=phy:/dev/vg/my_usr, target=/dev/sdb1, options=ro' ]
>
>I know its late in the day to be making changes like this, but it
>doesn't hurt to canvass opinion...
>
>
The only thing to think about is how do handle file devices with spaces
in the filename. This is going to be common I think.
Comma and spaces are valid filename characters. I think : is probably
the safest separator since it's used a lot.
>I'd also do away with all the fancy stuff we have to build the command
>line and just have a single command line variable that we assemble
>everything in to within the config file. The current magic just makes
>things more confusing.
>
>
Yes :-)
Regards,
Anthony Liguori
>Ian
>
>
>
>
>
>Ian
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2005-10-19 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 21:57 block-nbd script and example config Ian Pratt
2005-10-19 22:07 ` Anthony Liguori [this message]
2005-10-20 0:52 ` Nicholas Lee
2005-10-20 3:25 ` Anthony Liguori
2005-10-20 8:15 ` Arnd Schmitter
2005-10-19 22:12 ` Nivedita Singhvi
-- strict thread matches above, loose matches on Subject: below --
2005-10-26 22:00 Ian Pratt
2005-10-25 12:15 Ian Pratt
2005-10-24 16:08 Ian Pratt
2005-10-25 19:37 ` Anthony Liguori
2005-10-19 10:09 Kurt Garloff
2005-10-25 10:53 ` Ewan Mellor
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=4356C389.1080804@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=garloff@suse.de \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.