qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] qemu-fuse
Date: Wed, 27 Aug 2008 19:00:38 +0100	[thread overview]
Message-ID: <20080827180038.GB27491@shareable.org> (raw)
In-Reply-To: <48B580B5.8030804@codemonkey.ws>

Anthony Liguori wrote:
> 1) disable the root readable limitation in fuse, this has to be done 
> globally and I suspect is unlikely to be done by distros.

Can't you read even if you do the whole fuse setup as root (including
real user-id etc.)?

If that's a real problem with fuse in some applications, I'm surprised
there isn't at least an option, available only to root, to relax it.

Or maybe they just don't know about this scenario, and a fix would be
welcome...

> So that's why I settled on qemu-nbd.

Yeah, it's a really nice idea, thank you :-)

A FUSE-style "userspace block device" which doesn't require any root
access would be nice in principle, but qemu-nbd does the job and
doesn't require any add-ons.

-- Jamie

  parent reply	other threads:[~2008-08-27 18:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27 15:50 [Qemu-devel][PATCH] qemu-fuse Shahar Frank
2008-08-27 16:28 ` Anthony Liguori
2008-08-27 17:02   ` Luca Bigliardi
2008-08-27 18:00     ` Anthony Liguori
2008-08-27 18:10       ` Daniel P. Berrange
2008-08-27 18:59         ` Jamie Lokier
2008-08-28  8:03           ` Shahar Frank
2008-08-28  9:27             ` [Qemu-devel][PATCH] block level testing/execersing utility Shahar Frank
2008-08-28  9:47               ` Samuel Thibault
2008-08-28 12:22                 ` Shahar Frank
2008-08-28 20:11               ` Anthony Liguori
2008-08-27 18:00   ` Jamie Lokier [this message]
2008-08-28 21:05 ` [Qemu-devel] Re: [PATCH] qemu-fuse Szabolcs Szakacsits

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=20080827180038.GB27491@shareable.org \
    --to=jamie@shareable.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).