On Tue, 2014-10-21 at 16:03 +0200, Josselin Mouette wrote: > The Wanderer <wande...@fastmail.fm> wrote: > This is the problem. The init system should not be providing > "features" > which other software might, post-boot and pre-shutdown, want to make > use > of. (AFAIK sysvinit never did, and most - possibly all? - of the other > init-system candidates don't either.) Such features should be provided > separately, independent of what may happen to be running as PID 1. > > These features cannot exist separately. Quoting the systemd position > statement: > > […] while it is true that a handful of trivial interfaces are not really > related to systemd (and could be split out if needed), most of these > features cannot be implemented without close integration to PID 1. It is > not possible to split the system cgroups arbitrator from the process > which starts services and sessions in cgroups. It is not possible to > ensure the relation of a log to a service if you do not have awareness > of how the service was launched. Et caetera.
How is uselessd solving this then? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1413904376.15088.21.ca...@g3620.my.own.domain
