On Fri, Mar 20, 2015 at 1:56 AM, Kai Krakow <hurikha...@gmail.com> wrote: > > The point is: Let's just find out why the "intuitive" way to solve the OPs > problem doesn't work out and find the right solution. Let's face it: Trying > to use targets as sysvinit runlevels equivalent is obviously not the working > way although it looks promising and intuitive at first
sysinit.target and basic.target are exact equivalent of sysvinit runlevels - they are hard serialization points between groups of services so that systemd will not proceed with next group until all services in previous group are started. The difference is that these runlevels are hardcoded and not configurable. All that OP asked for was a way to make it more flexible and customizable. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel