From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MJl3q-0007gc-VF
	for qemu-devel@nongnu.org; Thu, 25 Jun 2009 05:16:03 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MJl3l-0007gI-Ax
	for qemu-devel@nongnu.org; Thu, 25 Jun 2009 05:16:01 -0400
Received: from [199.232.76.173] (port=46291 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MJl3l-0007gF-12
	for qemu-devel@nongnu.org; Thu, 25 Jun 2009 05:15:57 -0400
Received: from mx2.redhat.com ([66.187.237.31]:33634)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kwolf@redhat.com>) id 1MJl3k-0002zI-JH
	for qemu-devel@nongnu.org; Thu, 25 Jun 2009 05:15:56 -0400
Message-ID: <4A434009.5010009@redhat.com>
Date: Thu, 25 Jun 2009 11:14:49 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
References: <1245862739.6278.7.camel@localhost>
	<1245866233.6278.17.camel@localhost>
In-Reply-To: <1245866233.6278.17.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH] support colon in filenames
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: linuxram@us.ibm.com
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>

Ram Pai schrieb:
> Copying the qemu-devel mailing list too.
> 
> On Wed, 2009-06-24 at 09:58 -0700, Ram Pai wrote:
>> Problem: It is impossible to feed filenames with the character colon because 
>> qemu interprets such names as a protocol. For example  a filename scsi:0,
>> is interpreted as a protocol by name "scsi".
>>
>> This patch allows users to espace colon characters. For example the above filename
>> can now be expressed as 'scsi\:0'
>>
>> Here are couple of examples:
>>
>> ndb:\::9999  is treated as a ndb protocol with a hostname ':' on port 9999
>> scsi\:0\:abc is a local file scsi:0:abc
>> http\://myweb is a local file by name http://myweb
>> nbd\::localhost:2558  is a protocol by name nbd: 

Is there any use in having a host named : or protocol nbd:? I don't
think so. The other examples could be achieved much easier by assigning
the file: protocol to raw, so we would have:

file:scsi:0:abc
file:http://myweb

This solution wasn't accepted last time because it wouldn't solve the
problems with other characters like commas (they need to be escaped as
double comma on the command line) and that won't be solved by this patch
either.

Kevin