On Fri, May 24, 2013 at 01:45:46AM +0200, Matthias Klumpp wrote: > 2013/5/24 brian m. carlson <sand...@crustytoothpaste.net>: > > The Unix Way is to use separate processes > > for separate tasks. > ...and this is what systemd does! It's not like we have an > event-logger, hotkey-handling and seat-management all in pid0. It is > all nicely split into separate processes. The journal is mainly used > to produce structured logs and to log the early boot process (which I > find *very* nice, it helped me a lot already!), but you can turn it's > functionality off[1].
Yes, systemd uses separate processes, but they are not independent. They cannot be independently turned off. If I decide I do not want the journal features, however useful others might think they are, I should not have to resort to chmod and dpkg-statoverride to keep them from running. Let them be optional features which the core systemd can be used without. > There will be a reason why it cannot be removed completely too. > I think it is valid to see "systemd" as a compilation of basic tools > for a Linux system, which also includes an init-system. The problem is that it would be great as just an init system. I love it as an init system: it boots very, very fast and shuts down very, very fast. But that's all I want it to do: be an init system. I *have* a syslog daemon. I *have* tools to handle hotkeys. It should be a great init system, and (at least be able to be configured to be) *absolutely nothing else*: one small, limited process with PID 1. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
