Hello,
I'm facing a problem with Xen machines that depends on MD devices.
As I'm new to systemd world, I might not be seeing the clean solution.
That's why I'm asking for an advice.
MD devices are automatically detect by udev. If device state is safe,
/dev/md/myraid is started. However, if the
On Tue, 2017-09-12 at 13:26 +0200, Lennart Poettering wrote:
> On Mo, 11.09.17 23:33, Sébastien Luttringer (se...@seblu.net) wrote:
>
> > Hello,
> >
> > It appears that the nobody user/group are not created by systemd-sysusers,
> > despite its definition in sysusers.d/basic.conf.
> > I guess
On Tue, Sep 12, 2017 at 01:38:00PM +0200, Lennart Poettering wrote:
> On Mo, 11.09.17 11:47, Dmitry Torokhov (dmitry.torok...@gmail.com) wrote:
>
> > Previously we were loading kernel modules on all device events save
> > for "remove". With the introduction of KOBJ_BIND/KOBJ_UNBIND this causes
>
On Tue, Sep 12, 2017 at 2:38 PM, Lennart Poettering
wrote:
> But then, for single-patch PRs we don't do merges but
> rebase+fforward, which github has an explicit button in its UI
> for. But that rebase is kinda broken conceptually by them: it rewrites
> the commits of
On Mo, 11.09.17 23:33, Sébastien Luttringer (se...@seblu.net) wrote:
> 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
On Mo, 11.09.17 11:47, Dmitry Torokhov (dmitry.torok...@gmail.com) wrote:
> 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
>