[systemd-devel] Idea of splitting boot up logic from core

[cee1]

Hi all,

It seems too many branches in core:
* system mode in host
* system mode in container
* user mode

IMHO, the central concept of systemd is "units", hence it seems more
sensible to keep units related logic in core, and split boot up logic
in each "manager" running in:
1. system mode in host
2. system mode in container
3. user mode

This makes the boot up procedure ** more declarative **(no or less
branches, think about android's initrc)

And the central units logic is only for:
1. Tracking the dependencies among units
2. Schedule launch of units: confine them to meet the dependencies,
and *** make the best schedule decision ***, e.g. If A is a much more
dependent unit, do not start A with too many units in parallel



-- 
Regards,

- cee1