<html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 04/01/2016 10:11 AM, Vasiliy Tolstov wrote: </div> <blockquote cite="mid:CACaajQtL_b21QrQEnbn87ED3yixK7qOWLzNAP2U6CWq-VcTrBA@mail.gmail.com" type="cite"> <pre wrap="">2016-04-01 13:08 GMT+03:00 Jóhann B. Guðmundsson <a class="moz-txt-link-rfc2396E" href="mailto:johannbg@gmail.com"><johannbg@gmail.com></a>: </pre> <blockquote type="cite"> <pre wrap="">I dont see how you plan on implement this if not with either a secondary program loader which stores an redundant environment or an kernel support that does the similar/same thing I mean you need to have a watchdog support,boot counter which get's cleared when system decides it's up and stable,boot limit which tells it how many times it should try with an given entry, an entry which points to which kernel/image/snapshot to use right? I'm pretty sure Kay and Lennart must have thought things through so they just dont add just some half ass, none future proof, working solution that give administrators and embedded distribution fake notion of redundancy or a "fail-safe" when images and or kernel or the OS itself get's update/upgraded. If this cannot or will not be reliably implemented there is no point in implementing this in the first place from my pov. </pre> </blockquote> <pre wrap=""> In my POV - provide systemd service file that started after all stuff (may be this is systemd --user service or something like this) . I think that successful start - run my preferred DE. </pre> </blockquote> It would not be type units that would determine when boot is considered completed since you cannot reliably rely on that. 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". JBG </body> </html>