On Thu, Apr 12, 2012 at 4:56 AM, Lennart Poettering
wrote:
> I think I added this logic primarily to make the shutdown loop quiet.
>
> However I must admit that that's just a guess and since my commit
> message is disappointingly unconclusive about this I am a bit lost...
>
> If you revert f3accc0
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds after reaching the target, the device entries
show up.
Does that block or return immediately?
rmmod;
modprobe; time udevadm settle
Your driver creates the stuf
On Wed, 11.04.12 10:33, Daniel Drake (d...@laptop.org) wrote:
> Now, in systemd-shutdown we reach mount_points_list_get() in umount.c,
> which does:
>
> /* If we encounter a bind mount, don't try to remount
> * the source dir too early */
> skip_ro
'Twas brillig, and Daniel Drake at 11/04/12 17:33 did gyre and gimble:
> On Wed, Apr 11, 2012 at 9:40 AM, Lennart Poettering
> wrote:
>> So on shutdown after stopping all services we execute systemd-shutdown
>> as PID 1 replacing the normal systemd process. This is useful to drop
>> all references
