From: Arnd Schmitter <arnd_xen@yahoo.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Xen development list <xen-devel@lists.xensource.com>,
Kurt Garloff <garloff@suse.de>,
Nicholas Lee <emptysands@gmail.com>
Subject: Re: block-nbd script and example config
Date: Thu, 20 Oct 2005 10:15:05 +0200 [thread overview]
Message-ID: <43575209.7030902@yahoo.de> (raw)
In-Reply-To: <43570E19.5070509@us.ibm.com>
Anthony Liguori wrote:
> Nicholas Lee wrote:
>
>>> 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.
>>>
>>
>> Since it's a python variable can't you just run a validator on config
>> import and throw an exception if the devive block doesn't exist.
>> Noting that device paths including special characters need to be
>> enclosured in "...".
>>
>> ie. export=phy:"/dev/vgname/bob your uncle; mate! device", ...
>>
>>
> Double quotes are actually valid characters in a filename although
> rarely used.
>
> A more bold way of approaching this would be to adopt a more qemu like
> syntax of:
>
> hda1="/dev/vgname/bob you uncle; mate1"
> hda2="/root/rockhopper.img"
>
> We could use stat to figure out whether something was a file or a
> device and use the appropriate script (file or phy). For everything
> else, we could use explicit urls such as:
>
> hda3="nbd://rockhopper.austin.ibm.com:1025"
>
> I like the syntax a lot but I'm not sure that marking a device
> read-only works nicely anymore. We could have a single readonly
> attribute like:
>
> readonly=['hda1', 'hda2']
For readonly i would suggest a kind of following syntax:
hda1:r="/dev/..."
hda2:w="/dev/.."
Arnd
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
next prev parent reply other threads:[~2005-10-20 8:15 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
2005-10-20 0:52 ` Nicholas Lee
2005-10-20 3:25 ` Anthony Liguori
2005-10-20 8:15 ` Arnd Schmitter [this message]
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=43575209.7030902@yahoo.de \
--to=arnd_xen@yahoo.de \
--cc=aliguori@us.ibm.com \
--cc=emptysands@gmail.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.