From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HFuIN-0002NZ-A4
	for qemu-devel@nongnu.org; Sat, 10 Feb 2007 10:37:47 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HFuIK-0002MT-TJ
	for qemu-devel@nongnu.org; Sat, 10 Feb 2007 10:37:45 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HFuIK-0002MQ-Oc
	for qemu-devel@nongnu.org; Sat, 10 Feb 2007 10:37:44 -0500
Received: from nevyn.them.org ([66.93.172.17])
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
	(Exim 4.52) id 1HFuIK-0000Uj-Bo
	for qemu-devel@nongnu.org; Sat, 10 Feb 2007 10:37:44 -0500
Received: from drow by nevyn.them.org with local (Exim 4.63)
	(envelope-from <drow@nevyn.them.org>) id 1HFuII-000461-Ft
	for qemu-devel@nongnu.org; Sat, 10 Feb 2007 10:37:42 -0500
Date: Sat, 10 Feb 2007 10:37:42 -0500
From: Daniel Jacobowitz <drow@false.org>
Subject: Re: [Qemu-devel] Two quick requests.
Message-ID: <20070210153741.GA15685@nevyn.them.org>
References: <200702091719.16429.rob@landley.net>
	<200702092248.52614.paul@codesourcery.com>
	<c1bf1cf0702091459t1ffbab82q53777e76f0a6a116@mail.gmail.com>
	<200702092306.25097.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200702092306.25097.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
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: qemu-devel@nongnu.org

On Fri, Feb 09, 2007 at 11:06:24PM +0000, Paul Brook wrote:
> > Sure, but there are plenty of other ways to accidentally mess up the
> > permissions of a disk image file. A while back I had to strace qemu to
> > figure out why file modifications were vanishing after rebooting the
> > VM; the culprit turned out to be an unrelated script that had set the
> > image file's mode to 444.
> 
> If you really want to do this, do it properly. Make it an error to use a ro 
> image if the user [implicitly] requests rw access.

But if you do this please be sure not to complain about rw COW images
based on readonly ones...

-- 
Daniel Jacobowitz
CodeSourcery