[systemd-devel] systemd-nspawn trouble

[Michael Biebl]

2015-04-22 14:26 GMT+02:00 Lennart Poettering <lennart at poettering.net>:
> On Wed, 22.04.15 14:22, Michael Biebl (mbiebl at gmail.com) wrote:
>
>> 2015-04-22 14:14 GMT+02:00 Lennart Poettering <lennart at poettering.net>:
>> > On Wed, 22.04.15 14:09, Michael Biebl (mbiebl at gmail.com) wrote:
>> >
>> >> 2015-04-22 13:57 GMT+02:00 Lennart Poettering <lennart at poettering.net>:
>> >> >> Maybe we should simply list the iptables kernel modules in
>> >> >> src/core/kmod-setup, and then tell people to blacklist them if they
>> >> >> really don't want them.
>> >> >
>> >> > I have made such a change now:
>> >> >
>> >> > http://cgit.freedesktop.org/systemd/systemd/commit/?id=1d3087978a8ee23107cb64aa55ca97aefe9531e2
>> >>
>> >> 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.
>>
>> That's the wrong way around.
>
> Nah, I disagree. We do this for a number of modules now. I mean, we

We currently do this static loading for unix, ipv6 and autofs4.

> load tons of modules automatically, even if you don't use them. For
> example, my laptop always loads the bluetooth modules, even though I
> never used bluetooth.

Those are all loaded on demand, not statically. I.e. we don't load the
bluetooth module for each and every user.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?