bug#60246: Inability to add pseudo-filesystem fstab entries

[mirai]

Hi,

On 2022-12-21 22:50, Tobias Geerinckx-Rice wrote:
> 
> 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. 

If that's the case, an approach for these "unspeakable" file-systems whose 
presence must not be recorded in fstab
would be to at least "generate" some file-system- shepherd services (and have 
them enabled/disabled according to mount? value).
This way there's at least a way to "start" these mounts rather than them ending 
up in the /dev/null abyss.