[systemd-devel] systemd efi boot and default entry

[Tobias Hunger]

Hi Jóhann and Vasiliy,

IIRC both coreos and chormeOS only mark a boot as successful after
talking to their respective update servers. The assumption apparently
is that the OS can fix itself when it is able to communicate properly
with its own update server.

It would be nice if something similar could be implemented with
systemd in a straight-forward way IMHO.

Best Regards,
Tobias

On Fri, Apr 1, 2016 at 1:18 PM, Jóhann B. Guðmundsson
<johannbg at gmail.com> wrote:
>
>
> On 04/01/2016 10:52 AM, Vasiliy Tolstov wrote:
>>
>> 2016-04-01 13:50 GMT+03:00 Jóhann B. Guðmundsson <johannbg at gmail.com>:
>>>
>>> AFAIK the android boot process fires an standard broadcasting action
>>> "ACTION_BOOT_COMPLETED" once system services are up and running in
>>> memory,
>>> which is the time when it considered the boot being completed and
>>> "stable".
>>
>>
>> Thanks, how about ChromeOS ?
>>
>
> Dont know, dont care. Upstart ( which ChromeOS uses as it's init system ) is
> history...
>
> JBG
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel