Re: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

[Mike Gilbert <floppym@xxxxxxxxxx>]

On Mon, Feb 8, 2021 at 2:31 PM Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
> > I think removing this symlink would prevent /sys/fs/fuse/connections
> > from being mounted and the fuse module from being loaded
> > unconditionally on boot
>
> no
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1909805#c6

It almost works for me on Gentoo Linux.
To test, I first had to reconfigure my kernel to build FUSE as a
module (I normally have it built-in).
I then removed the sys-fs-fuse-connections.mount symlink from
sysinit.target.wants.
After rebooting with the new kernel, the FUSE module is not loaded and
/sys/fs/fuse/connections is not mounted.

Unfortunately, mounting FUSE-based file systems does not work until I
manually run "modprobe fuse".
It seems that my kernel does not auto-load the module, despite the
static /dev/fuse node. The kernel is probably missing a call to
__request_module().

Given that the kernel doesn't auto-load the module on demand, leaving
the sysinit.target.wants symlink in place seems like the safe thing to
do.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel