2016-04-01 13:08 GMT+03:00 Jóhann B. Guðmundsson <johan...@gmail.com>: > 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.
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. -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
