From: Eric Blake <eblake@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>
Cc: Klaus Kiwi <kkiwi@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [qemu-web PATCH] Update FUSE block export blog post
Date: Tue, 7 Sep 2021 12:52:16 -0500 [thread overview]
Message-ID: <20210907175216.dze5fvinpo5pxlt2@redhat.com> (raw)
In-Reply-To: <20210906162916.21714-1-hreitz@redhat.com>
On Mon, Sep 06, 2021 at 06:29:16PM +0200, Hanna Reitz wrote:
> Because I forgot to CC Thomas on the discussion adding this post, it was
> merged prematurely. This patch updates the post to incorporate the
> feedback I received on it:
>
Overall, nice! I see it's already live, but another tweak you might
want to make:
> +## File mounts
>
> -A perhaps little-known fact is that, on Linux, filesystems do not need to have
> -a root directory, they only need to have a root node. A filesystem that only
> -provides a single regular file is perfectly valid.
> +To transparently translate a file into a different format, like we did above, we
> +make use of two little-known facts about filesystems and the VFS on Linux. The
> +first one of these we can explain immediately, for the second one we will need
> +some more information about how FUSE exports work, so that secret will be lifted
s/lifted/revealed/
> +later (down in the “Mounting an image on itself” section).
> +
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2021-09-07 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 16:29 [qemu-web PATCH] Update FUSE block export blog post Hanna Reitz
2021-09-07 14:07 ` Thomas Huth
2021-09-07 15:54 ` Hanna Reitz
2021-09-07 17:52 ` Eric Blake [this message]
2021-09-14 10:02 ` Hanna Reitz
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=20210907175216.dze5fvinpo5pxlt2@redhat.com \
--to=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kkiwi@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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).