| Hmm, I was expecting "Sorry we made a mistake, we'll switch the option to systemd.debug". > At that point there is simply no other option for that, because persistent storage is not available This was about overloading an already used option by another team building a core system component -- the kernel. A debug for kernel's command line is for the kernel. > It's the option an admin can specify which tells him why the system doesnt boot, Ok so he does and now his system also doesn't boot but now it is either because of the original problem or because it gets flooded by systemd logs. And then, he goes and posts to the kernel mailing lists saying how kernel is a piece of shit. > That turns this into some kind of power game, which I am totally not interested in. also > We are putting together an OS here after all, not just a kernel, and a kernel is just one component of the OS among many, and ultimately an implementation detail. I think due to their attitude towards both testing, towards the kernel community, they shouldn't be building core system components. And did he just write that kernel is just "an implementation detail?". Maybe systemd was a mistake. Integrating and dumping socket acceptors, logging, and the whole kitchen sink into one component. So when it breaks it really breaks. |
In theory, systemd could be made to work on BSDs, Hurd, Minix, or whatever.
In reality, I'd sooner expect systemd to provide it's own kernel, but you never know.