Bug#799244: Algortihm does not work like in: libkmod-module: fix return code in error path

fin4478 fin4478 fin4478 at hotmail.com
Fri Sep 18 14:10:13 BST 2015


Plaa plaa, read kernel documentation:
CONFIG_AUTOFS4_FS:

The automounter is a tool to automatically mount remote file systems
on demand. This implementation is partially kernel-based to reduce
overhead in the already-mounted case; this is unlike the BSD
automounter (amd), which is a pure user space daemon.


To use the automounter you need the user-space tools from
<ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
want to answer Y to "NFS file system support", below.

To compile this support as a module, choose M here: the module will be
called autofs4. You will need to add "alias autofs autofs4" to your
modules configuration file.

If you are not a part of a fairly large, distributed network or
don't have a laptop which needs to dynamically reconfigure to the
local network, you probably do not need an automounter, and can say
N here.


Millions of home computers are not in a large distributed network, so systemd politics is stupid. Every unneeded module and message slows your computer.

On Fri, 18 Sep 2015 11:05:51 +0200
Michael Biebl <biebl at debian.org> wrote:

> Am 18.09.2015 um 02:53 schrieb Michael Biebl:
> > Am 18.09.2015 um 02:01 schrieb fin4478 fin4478:
> >> "This is already part of
> >> v226"
> >>
> >> Im trying to get rid of boot messages: Using lastest kmod
> >> https://git.kernel.org/cgit/utils/kernel/kmod/kmod.git/commit/?id=114ec87c85c35a2bd3682f9f891e494127be6fb5
> >>
> >> fixes this:
> >> systemd[1]: Failed to insert module 'kdbus'
> >>
> >> But using systemd 266 throws:
> >> systemd[1]: Failed to insert module 'autofs4'
> >>
> >> I have made 2 custom kernel for 2 Debian Stretch PC. Kernel 4.1.3 and 4.3 and I disabled autofs in kernel configuration, same happens in both systems. Setting LogLevel=crit in /etc/systemd/system.conf has no effect.
> >>
> >> >From the systemd code you can see that blacklisting autofs4 might help, but there is no sense to blacklist modules that do not exist in the kernel.
> > 
> > This is deliberate, autofs4 has the "warn_if_unavailable" flag set,
> > kdbus hasn't.
> > Nothing to fix here, especially downstream.
> 
> As for further explanation: systemd provides a unit type called
> automount [1] which requires autofs support from the kernel. Without
> that support, that functionality is broken. systemd even ships automount
> units by default.
> The warning is thus appropriate, since the user might accidentally have
> disabled autofs in the kernel.
> 
> Michael
> 
> 
> 
> [1] http://www.freedesktop.org/software/systemd/man/systemd.automount.html
> [2] $ systemctl list-units --type=automount
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 




More information about the Pkg-systemd-maintainers mailing list