cursed as fuck

The Technical Quality
This book has multiple technical inaccuracies. This is
especially impressive because it is almost entirely
devoid of technical content. This is, somehow, smut in
dire need of a technical editor
The most egregious falsehood is definitely the
statement that "you can't use shared libraries for init,
that just wouldn't make sense."
That is flat-out wrong. have yet to see a statically
linked copy of systemd. don't think systemd's build
system even provides support for creating sucha
binary. It absolutely makes sense for systemd
(typically at /usr/lib/systemd/systemd) to rely
dynamically linked libraries in /usr/lib since, well,
mounting filesystem containing init is the job of the
kernel and/or the initrd.
Shortly thereafter, the author writes "init shouldn't
have a DHCP client in it", implying that it's the PID 1
systemd executable acting as a DHCP client, which of
course is not the case. This one isn't so bad though. It's
a greatest hit of systemd haters, so can totally
understand why he'd want to repeat it.
At one point, Systemd says that "if init doesn't let a
process exit, it doesn't exit until init is finished with
it." This statement is also inaccurate. There's nothing
systemd can about a process exiting. Yes, if it's an
orphan it can delay doing some cleanup, but that's a
rather atypical case. For the average process, systemd
has no say nor way to stop a process from exiting.
Next up, the author writes could see Google
addresses hard-coded right into [the DNS resolver]."
This is another sort of thing, but it's