3 ms·
> 73 binaries, each optional, easily replaceable. Except for the journal. It is effectively required by systemd (the pid 1 binary). In the vast majority of cas
by zbentley 8y ago
> 73 binaries, each optional, easily replaceable.
Except for the journal. It is effectively required by systemd (the pid 1 binary). In the vast majority of cases, that means running systemd-journald.
Every attempt I have seen at operating without it either misses early logs or is extremely fragile/unsupported.
That's a point of fact, not a position in the larger argument here. There are good arguments as to why journald should be effectively a required component.
> /lib/systemd/systemd, the PID 1 process, only starts processes, nothing else.
That is incorrect. It also interacts with the journal, the component implicated in the exploit in the article.
- theamk 8y ago> Except for the journal. It is effectively required by systemd (the pid 1 binary). In the vast majority of cases, that means running systemd-journald. man systemd ... --log-target= Set log target. Argument must be one of console, journal, kmsg, journal-or-kmsg, null. you can log to kmsg -- the messages won't be lost. > Every attempt I have seen at operating without it either misses early logs or is extremely fragile/unsupported. I am not surprised -- this was one of many annoying parts of sysvinit, the missing early userspace logs. This was one of the many annoying parts. Gentoo used to have a hacky way that scraped screen buffer (!) but I think it broke at some point[1]. > That is incorrect. It also interacts with the journal, the component implicated in the exploit in the article. Fair enough, I oversimplified. It also interacts with udev, systemctl, and does cronjob handling and network interface renaming. [1] I just checked Gentoo's website now and looks like they have a better way now due to OpenRC.