From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Two quick requests.
Date: Sat, 10 Feb 2007 10:37:42 -0500 [thread overview]
Message-ID: <20070210153741.GA15685@nevyn.them.org> (raw)
In-Reply-To: <200702092306.25097.paul@codesourcery.com>
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
next prev parent reply other threads:[~2007-02-10 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 22:19 [Qemu-devel] Two quick requests Rob Landley
2007-02-09 22:27 ` Paul Brook
2007-02-09 22:33 ` Rob Landley
2007-02-09 22:33 ` Dan Shearer
2007-02-09 22:48 ` Paul Brook
2007-02-09 22:59 ` Ed Swierk
2007-02-09 23:06 ` Paul Brook
2007-02-10 15:37 ` Daniel Jacobowitz [this message]
2007-02-12 17:27 ` Rob Landley
2007-02-12 17:45 ` Paul Brook
2007-02-12 18:17 ` Jan Marten Simons
2007-02-10 11:53 ` CAP_NET_ADMIN (was Re: [Qemu-devel] Two quick requests.) Kevin F. Quinn
2007-02-10 15:11 ` Paul Brook
2007-02-12 9:49 ` Chris Friedhoff
2007-02-12 23:25 ` [Qemu-devel] QEMU and SMP Option on dual core processor Danny Chieh-Yao, Cheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070210153741.GA15685@nevyn.them.org \
--to=drow@false.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.