On Di, 28.07.20 13:02, Tomasz Kłoczko (kloczko.tomasz@xxxxxxxxx) wrote: > So .. someone knows why it cannot be mounted on "mount -a" when entry > for binfmt_misc would be in fstab or even over .mount unit? You can do that, of course, but binfmt_misc is a .ko we don't want to load unless needed. With the scheme we have right now we'll load it only when someone fiddles with the binfmt_misc dir. > IMO using automounter to mount sysfs, procfs and binfmt_misc is really > OVERKILL. We don't use the automounter for sysfs or procfs, that would make little sense. These file systems are mounted early on from PID 1, before doing pretty much anything else, since much of the Linux kernel's API we need is exposed through these virtual file systems. binfmt_misc is kinda an exotic feature though, and unless you install java or mono or qemu for foreign archs you are unlikely to use it. > If the regular unit works flawlessly it looks like systemd could be > compiled without autofs. You can compile it without autofs. But why bother? it's tiny and useful. > For example mqueue is mounted over .mount unit > > $ cat /usr/lib/systemd/system/dev-mqueue.mount | grep -v \# > [Unit] > Description=POSIX Message Queue File System > Documentation=man:mq_overview(7) > Documentation= > https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems > DefaultDependencies=no > Before=sysinit.target > ConditionPathExists=/proc/sys/fs/mqueue > ConditionCapability=CAP_SYS_ADMIN > > [Mount] > What=mqueue > Where=/dev/mqueue > Type=mqueue > Options=nosuid,nodev,noexec > > Looks like all other pseudo filesystems are mounted over .mount units with > probably one exception .. binfmt_misc. > Probably .. because as I've pointed there are two units for that fs. Only binfmt_misc is typically a kernel module of its own. For stuff that is built-in it's pointless trying to avoid module loading. Lennart -- Lennart Poettering, Berlin _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
