From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HGfkA-0006XY-E5 for qemu-devel@nongnu.org; Mon, 12 Feb 2007 13:17:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HGfk8-0006Wn-FN for qemu-devel@nongnu.org; Mon, 12 Feb 2007 13:17:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HGfk8-0006Wj-BE for qemu-devel@nongnu.org; Mon, 12 Feb 2007 13:17:36 -0500 Received: from mta-2.ms.rz.rwth-aachen.de ([134.130.7.73]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.52) id 1HGfk8-0005hu-3a for qemu-devel@nongnu.org; Mon, 12 Feb 2007 13:17:36 -0500 Received: from r220-1 ([134.130.3.31]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JDD007Y1459D570@mta-2.ms.rz.RWTH-Aachen.de> for qemu-devel@nongnu.org; Mon, 12 Feb 2007 19:17:33 +0100 (CET) Received: from [137.226.40.101] (pc42.xtal.RWTH-Aachen.DE [137.226.40.101]) by relay.rwth-aachen.de (8.13.7/8.13.3/1) with ESMTP id l1CIHWan001149 for ; Mon, 12 Feb 2007 19:17:32 +0100 (MET) Date: Mon, 12 Feb 2007 19:17:42 +0100 From: Jan Marten Simons Subject: Re: [Qemu-devel] Two quick requests. In-reply-to: <200702121227.47557.rob@landley.net> Message-id: <45D0AF46.8080909@xtal.rwth-aachen.de> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT References: <200702091719.16429.rob@landley.net> <200702092306.25097.paul@codesourcery.com> <200702121227.47557.rob@landley.net> 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 Rob Landley schrieb: > On Friday 09 February 2007 6:06 pm, 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. >> > > If there's no middle ground between "silently misbehave" and "refuse to start > if anything _might_ be wrong", then why does current qemu warn about the 1024 > hz thing? > > Just curious. Refusing to start would have saved me a day's debugging time, > just like the warning would have... > > Rob > I think adding a simple (suppressable) warning on startup would be sufficient in case of a ro image. Jan