From: Tobias Geerinckx-Rice <me@tobias.gr>
To: h.goebel@crazy-compilers.com, guix-devel@gnu.org
Subject: Re: Curious unionfs-ro-mount for /gnu/store in installation-image
Date: Sun, 29 Oct 2017 18:30:04 +0100 [thread overview]
Message-ID: <a7e8d4ca-1bc4-ffd9-32ca-75703abd7e07@tobias.gr> (raw)
In-Reply-To: <de29f139-af5c-a367-1aa1-c0365c2a5466@crazy-compilers.com>
Hartmut,
Hartmut Goebel wrote on 29/10/17 at 18:18:
> immediately after booting the installation image (build according to [1]
> and run according to [2]), the "mount" command spits out *two* unionfs
> mounted points:
[...]
> But I'm curious, where the second one comes from. I've been searching
> this for two or three hours now and did not find, where this is defined.
Running the same ‘mount’ command on my GuixSD returns a hint:
nckx@apollo.tobias.gr ~$ mount
/dev/mapper/root on / type ext4 (rw,relatime,data=ordered)
/dev/mapper/root on /gnu/store type ext4 (ro,relatime,data=ordered)
> - gnu/system/install.scm defines the system to be put into the
> installation image. Thuns I thought it may be a file-system defined in
> install.scm. But related to the store there is only %immutable-store,
> which does not use unionfs a ro-bind-mount, not a unionfs.
I think this is all that's going on, and it's merely the output of
‘mount’ that's confusing you: the ‘ro’ bind mount ‘inherits’ the file
system type of the parent. In my example above, it's ext4. In yours,
it's fuse.unionfs.
Unless I'm missing something.
Kind regards,
T G-R
next prev parent reply other threads:[~2017-10-29 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 17:18 Curious unionfs-ro-mount for /gnu/store in installation-image Hartmut Goebel
2017-10-29 17:30 ` Tobias Geerinckx-Rice [this message]
2017-10-29 17:45 ` Hartmut Goebel
2017-10-31 1:56 ` Chris Marusich
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7e8d4ca-1bc4-ffd9-32ca-75703abd7e07@tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).