unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: mirai <mirai@makinata.eu>
Cc: 60246@debbugs.gnu.org
Subject: bug#60246: Inability to add pseudo-filesystem fstab entries
Date: Wed, 21 Dec 2022 23:50:08 +0100	[thread overview]
Message-ID: <87cz8c8hoc.fsf@nckx> (raw)
In-Reply-To: <ccb0ccf0-624c-b43f-cdce-8f0715e8eff2@makinata.eu>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

Hi Bruno,

mirai 写道:
> Does not result in a fstab entry line, which makes it impossible 
> to mount. According to Guix docs, this shouldn't be the case:

Hm, yes, strictly speaking that is so.

It feels a bit weird to add or omit fstab entries based on MOUNT? 
being true or false, but… it seems like a good proxy for what the 
user *means* in both cases?

If the following is really true, we have little other choice:

> ;; In particular, things like GIO (part of GLib) use it to 
> determine the set
> ;; of mounts, which is then used by graphical file managers and 
> desktop
> ;; environments to display "volume" icons.  Thus, we really need 
> to exclude
> ;; those pseudo file systems from the list.

so I wouldn't be opposed to it.

>                         %pseudo-file-system-types)

I disagree that overlayfs is a ‘pseudo-file-system’, any more than 
NFS would be.  It should not be in that list to begin with.

And this is where it gets fun: apparently… it was added at my 
request‽ :-)

Or at least Ludo's interpretation of that requests, in commit 
df1eaffc3:

    file-systems: Expound '%pseudo-file-system-types'.
    
    Reported by Tobias Geerinckx-Rice <me@tobias.gr>.
    
    * gnu/system/file-systems.scm (%pseudo-file-system-types): Add
    "debugfs", "efivarfs", "hugetlbfs", "overlay", and 
    "securityfs".

Even in this list, ‘overlayfs’ has huge 
one-of-these-is-not-like-the-others energy, so I wonder what the 
reason was.  I don't remember.

I'd happily revert it if I didn't suspect that it was to work 
around some real (installer?) bug…

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-12-21 23:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 21:19 bug#60246: Inability to add pseudo-filesystem fstab entries mirai
2022-12-21 22:50 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-12-21 23:37   ` mirai
2022-12-21 23:41     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=87cz8c8hoc.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=60246@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=mirai@makinata.eu \
    /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).