From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LL525-0007Qi-OZ for qemu-devel@nongnu.org; Thu, 08 Jan 2009 19:15:25 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LL523-0007PL-Vc for qemu-devel@nongnu.org; Thu, 08 Jan 2009 19:15:25 -0500 Received: from [199.232.76.173] (port=52557 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LL523-0007PG-RF for qemu-devel@nongnu.org; Thu, 08 Jan 2009 19:15:23 -0500 Received: from mail2.shareable.org ([80.68.89.115]:51337) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LL522-0003rt-O8 for qemu-devel@nongnu.org; Thu, 08 Jan 2009 19:15:22 -0500 Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from ) id 1LL51y-0003kj-ON for qemu-devel@nongnu.org; Fri, 09 Jan 2009 00:15:18 +0000 Date: Fri, 9 Jan 2009 00:15:18 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] qemu: block.c: introducing "fmt:FMT:" prefix to image-filenames Message-ID: <20090109001518.GD12848@shareable.org> References: <496642BD.4010706@redhat.com> <20090108185256.GA8669@redhat.com> <49664F54.7050908@redhat.com> <20090108191301.GB8669@redhat.com> <496650ED.1060602@redhat.com> <20090108231854.GB12848@shareable.org> <49668B01.60002@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49668B01.60002@codemonkey.ws> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Anthony Liguori wrote: > >Just because I hate hidden "some filenames work, some filenames break > >mysteriously, and of course it's not documented" dodgy hacks. > > > > I'm pretty certain that you couldn't do that today in QEMU. The colon > has always been used for protocol checking and if the protocol is > invalid, I think we throw an error. That sounds like a prime example of "some filenames break today already and of course it's not documented" :-) My own kvm/qemu management scripts create symlinks to the disk images and pass the symlink names to kvm/qemu instead of the real names for this reason... And also because what you can enter in the monitor "change" command isn't quite the same as what you can put on the command line. -- Jamie