All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] qemu-fuse
Date: Wed, 27 Aug 2008 13:00:27 -0500	[thread overview]
Message-ID: <48B5963B.9000906@codemonkey.ws> (raw)
In-Reply-To: <20080827170228.GG3644@pintsize>

Luca Bigliardi wrote:
> On Wed, Aug 27, 2008 at 11:28 AM, 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.
>>     
>
> 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.

Why don't you like qemu-nbd?  FWIW, I'm open to fuse but I don't think 
we should have both an NBD server and a fuse filesystem.  I think we 
should try and have a single mechanism to access guest images.

Regards,

Anthony Liguori

> Thank you,
>
> luca
>
>   

  reply	other threads:[~2008-08-27 18:01 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 [this message]
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   ` [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=48B5963B.9000906@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.