4 ms·
> Meantime, systemd is now taking over my logs, network, device tree, time service, cron, and more. This is a misrepresentation. It does have components for al
by Quekid5 7y ago
> Meantime, systemd is now taking over my logs, network, device tree, time service, cron, and more.
This is a misrepresentation. It does have components for all of those things, but AFAIK only journald and udev (I think) are non-optional. You're free to use cron, chrony (NTP), NetworkManager (or whatever), etc.
- dredmorbius 7y agoThe point isn't what I can or can't do (though I'm finding the encroachment despite my attempts to avoid it), the point remains that was billed as faster boot times. It's become vastly more than that. Source: the central responsibility of an init system is to bring up userspace. And a good init system does that fast. Unfortunately, the traditional SysV init system was not particularly fast. http://0pointer.de/blog/projects/systemd.html http://0pointer.de/blog/projects/systemd.html And in case that's been modified, the earliest archived version: https://web.archive.org/web/20100503054610/0pointer.de/blog/projects/systemd.html https://web.archive.org/web/20100503054610/0pointer.de/blog/... Discussed on HN at the time: https://news.ycombinator.com/item?id=1308367 https://news.ycombinator.com/item?id=1308367 And on LWN: https://lwn.net/Articles/385536/ https://lwn.net/Articles/385536/ Also on LWN, "Systemd as Tragedy", from January 2019: https://lwn.net/Articles/777595/ https://lwn.net/Articles/777595/ Also discussed on HN: https://news.ycombinator.com/item?id=19023232 https://news.ycombinator.com/item?id=19023232