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 c
> > 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
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 turn
Have a look here with links and a description:
http://www.friedhoff.org/fscaps.html
http://www.friedhoff.org/fscaps.html#Qemu
Serges patch is in the mm tree.
Chris
On Sat, 10 Feb 2007 15:11:00 +
Paul Brook <[EMAIL PROTECTED]> wrote:
> > Is there any way around this? I expected to be able
On Fri, Feb 09, 2007 at 11:06:24PM +, 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 culpri
> Is there any way around this? I expected to be able to configure
> capabilities for executables in the filesystem, but it appears there
> are serious problems with that concept so the kernel doesn't support
> it.
Use tunctl to create the device.
Paul
_
"Kevin F. Quinn" <[EMAIL PROTECTED]> wrote:
> On Fri, 9 Feb 2007 22:48:51 +
> Paul Brook <[EMAIL PROTECTED]> wrote:
>
> > I've very little sympathy (read: none) for people who "accidentally"
> > break things by running them as root.
>
> On a related note, I've been running qemu(-system
On Fri, 9 Feb 2007 22:48:51 +
Paul Brook <[EMAIL PROTECTED]> wrote:
> I've very little sympathy (read: none) for people who "accidentally"
> break things by running them as root.
On a related note, I've been running qemu(-system 0.8.2) as root
recently as a hopefully temporary measure so that
> 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
On 2/9/07, Paul Brook <[EMAIL PROTECTED]> wrote:
I've very little sympathy (read: none) for people who "accidentally" break
things by running them as root.
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
On Friday 09 February 2007 22:33, Dan Shearer wrote:
> On Fri, Feb 09, 2007 at 10:27:08PM +, Paul Brook wrote:
> > On Friday 09 February 2007 22:19, Rob Landley wrote:
> > > 1) When you accidentally run qemu as root, could it NOT try to go into
> > > a full-screen display by default resulting i
On Fri, Feb 09, 2007 at 10:27:08PM +, Paul Brook wrote:
> On Friday 09 February 2007 22:19, Rob Landley wrote:
> > 1) When you accidentally run qemu as root, could it NOT try to go into a
> > full-screen display by default resulting in a corrupted display you can't
> > break out of and have to
On Friday 09 February 2007 5:27 pm, Paul Brook wrote:
> On Friday 09 February 2007 22:19, Rob Landley wrote:
> > 1) When you accidentally run qemu as root, could it NOT try to go into a
> > full-screen display by default resulting in a corrupted display you can't
> > break out of and have to power
On Friday 09 February 2007 22:19, Rob Landley wrote:
> 1) When you accidentally run qemu as root, could it NOT try to go into a
> full-screen display by default resulting in a corrupted display you can't
> break out of and have to power cycle the machine?
This is a feature of your SDL libraries. T
1) When you accidentally run qemu as root, could it NOT try to go into a
full-screen display by default resulting in a corrupted display you can't
break out of and have to power cycle the machine?
2) After said reboot, when you're sanely running qemu as a normal user but
using the hda image fil
15 matches
Mail list logo
