On Wed, 22.04.15 14:28, Michael Biebl (mbi...@gmail.com) wrote: > 2015-04-22 14:22 GMT+02:00 Michael Biebl <mbi...@gmail.com>: > > 2015-04-22 14:14 GMT+02:00 Lennart Poettering <lenn...@poettering.net>: > >> On Wed, 22.04.15 14:09, Michael Biebl (mbi...@gmail.com) wrote: > >> > >>> Not everyone is using networkd or nspawn though, so loading this > >>> module for everyone is a bit excessive. > >> > >> Well, then blacklist the module or don't build it at all. > > [..] > > >> For the same reason that iptables doesn't complain loudly but loads > >> it. To be user-friendly and just make things work? > > And making everyone who doesn't want this feature jump through hoops > and having them blacklist the module is not user-friendly at all. > Least of it, it's not really intuitive and discoverable, how this > module got loaded in the first place.
Well, it is not discoverable for *any* kmod really, not just this one. Except, that this is actually *more* discoverable thant normal udev-based or kernel-auto-loaded kmods, since we actually *do* log about it, in contrast to those cases. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
