[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] A different way to ask for readonly drive
From: |
Jamie Lokier |
Subject: |
Re: [Qemu-devel] [PATCH] A different way to ask for readonly drive |
Date: |
Thu, 17 Dec 2009 15:30:16 +0000 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Kevin Wolf wrote:
> Am 17.12.2009 14:16, schrieb Jamie Lokier:
> You can decide to protect your images with the qemu readonly option and
> get the protection that qemu defines, or you take the permissions of the
> OS and get from the OS whatever the definition of that protection is
> (including write access for root).
Note that until the latest patch, "chmod 444" was the _the_ user
interface to this feature of qemu. It's a bad interface, but it was
the only one available. qemu is weird like that, having external
file permissions control an internal behaviour switch.
> qemu can't and shouldn't know that you use the OS's protection but
> actually don't quite mean what it's defined to be.
Then I concur with Christopher Hellwig, and we should drop the "auto"
behaviour entirely, and force the user interface to be the qemu
command line instead of "chmod" from now one.
-- Jamie
Re: [Qemu-devel] [PATCH] A different way to ask for readonly drive, Kevin Wolf, 2009/12/15
Re: [Qemu-devel] [PATCH] A different way to ask for readonly drive, Richard W.M. Jones, 2009/12/17