From: Jamie Lokier <jamie@shareable.org>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] qemu-fuse
Date: Wed, 27 Aug 2008 19:59:09 +0100 [thread overview]
Message-ID: <20080827185908.GF27491@shareable.org> (raw)
In-Reply-To: <20080827181031.GI27669@redhat.com>
> > >I'm sorry, why you don't like to pass '-o allow_root' to fuse_main() from
> > >your application ?
> > >
> >
> > It also requires user_allow_root to be specified in /etc/fuse.conf.
You need root access to use qemu-nbd (to mount it), and if you mount
as root you don't need to modify /etc/fuse.conf, so they're equivalent
in this regard.
> Well qemu-nbd also allows sharing to remote machines, whereas fuse
> only exposes it locally. qemu-nbd also allows access to things which
> aren't filesystems. eg, you could have LVM / software RAID devices
> inside your qcow file - qemu-fuse won't help you get access to those.
Yes, qemu-nbd lets you use all the kernel filesystems, different
partition formats, RAID, encryption etc.
-- Jamie
next prev parent reply other threads:[~2008-08-27 18:59 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 [this message]
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 ` [Qemu-devel][PATCH] qemu-fuse Jamie Lokier
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=20080827185908.GF27491@shareable.org \
--to=jamie@shareable.org \
--cc=berrange@redhat.com \
--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).