[systemd-devel] RootImage='s implementation

Hi list,After looking at the code that implements the RootImage= directive, I was wondering why it was necessary to do this in PID 1 (code seems to have been partially borrowed from what nspawn uses), and why was RootImage= not internally converted to RootDirectory=/run/some/private/dir/ where

Re: [systemd-devel] Race condition between udev rules and hwdb

On Tue, Feb 06, 2018 at 09:14:46AM +0200, Mantas Mikulėnas wrote: > On Tue, Feb 6, 2018 at 1:21 AM, Peter Hutterer > wrote: > > > On Mon, Feb 05, 2018 at 11:51:30AM +0200, Mantas Mikulėnas wrote: > > > On Mon, Feb 5, 2018 at 8:02 AM, Peter Hutterer

Re: [systemd-devel] Why is systemd-run --scope synchronous?

On Tue, 06 Feb 2018 at 13:09:26 +0100, worz wrote: > I am not sure why things are different. I also > notice the difference is that in case of --scope, the service manager is > not really the parent process, and it's just that systemd-run creates a > transient scope and places the process inside

[systemd-devel] Why is systemd-run --scope synchronous?

Sorry for the badly formatted emails, I'll use a different provider thatactually allows sending plain-text emails next time. I could only noticeafter it was sent. Yes, I meant it in terms of foreground vs background. For example, not  specifying --scope just pushes it into a service, while with