[systemd-devel] systemd-sysusers does not create nobody user

2017-09-11 Thread Sébastien Luttringer
Hello, It appears that the nobody user/group are not created by systemd-sysusers, despite its definition in sysusers.d/basic.conf. I guess nss_systemd is always providing answers for nobody user/group which mislead systemd-sysusers. # grep nobody /etc/passwd; echo $? 1 # getent passwd nobody nobo

Re: [systemd-devel] [PATCH] rules: load drivers only on "add" events

2017-09-11 Thread Mantas Mikulėnas
On Mon, Sep 11, 2017, 21:48 Dmitry Torokhov wrote: > As a side note, I am confused about handling authorship information in > systemd repository. The commit 9a39e1ce314d1a6f8a754f6dab040019239666a9 > adding handling of bind/unbind actions is clearly taken from the email I > posted on systemd-deve

Re: [systemd-devel] [PATCH] rules: load drivers only on "add" events

2017-09-11 Thread systemd github import bot
Patchset imported to github. To create a pull request, one of the main developers has to initiate one via: -- Generated by https://github.com/haraldh/mail2git ___

[systemd-devel] [PATCH] rules: load drivers only on "add" events

2017-09-11 Thread Dmitry Torokhov
Previously we were loading kernel modules on all device events save for "remove". With the introduction of KOBJ_BIND/KOBJ_UNBIND this causes issues, as driver modules that have devices bound to their drivers get immediately reloaded, and it appears to the user that module unloading does not work.