From: Jim Fehlig <jfehlig@novell.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools/hotplug/Linux/blktap: remove optional tapdisk: prefix
Date: Mon, 19 Apr 2010 21:02:46 -0600 [thread overview]
Message-ID: <4BCD1956.4040607@novell.com> (raw)
In-Reply-To: <4BCC24A8020000780003AC70@novell.com>
Jan Beulich wrote:
>>>> Jim Fehlig <jfehlig@novell.com> 16.04.10 22:51 >>>
>>>>
>> Jan Beulich wrote:
>>
>>> Perhaps this should even be further generalized (e.g. to remove any
>>> "[!/]*:" pattern prefixes) to be more forward compatible?
>>>
>>>
>> Right. Need to handle the 'ioemu' subtype as well. How about just
>> stripping of everything before the leading '/'? E.g. like the attached
>> patch?
>>
>
> Wouldn't that become wrong when remote locations are acceptable
> here (not sure if they aren't already), i.e. server:/path/file?
IMO, remote locations should be handled by another tap driver optimized
for the remote file protocol, similar to the nbd, curl, etc. block
backends in qemu.
> If that
> is not expected to ever have a meaning and if relative paths aren't
> permitted here, then yes, that would of course be the best solution.
>
The tools currently don't cope with relative paths in disk specification.
Jim
prev parent reply other threads:[~2010-04-20 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 10:13 [PATCH] tools/hotplug/Linux/blktap: remove optional tapdisk: prefix Jan Beulich
2010-04-16 20:51 ` Jim Fehlig
2010-04-19 7:38 ` Jan Beulich
[not found] ` <4BCC24A8020000780003AC70@novell.com>
2010-04-20 3:02 ` Jim Fehlig [this message]
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=4BCD1956.4040607@novell.com \
--to=jfehlig@novell.com \
--cc=JBeulich@novell.com \
--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.