3 ms·
OpenBSD finally got installed because I had a corner case where Linux cannot rein in the misbehaving systemd. This corner case is where I must block all networ
by egberts1 6y ago
OpenBSD finally got installed because I had a corner case where Linux cannot rein in the misbehaving systemd.
This corner case is where I must block all network access with and by systemd.
systemd DHCP is still immature in dealing with Juniper DHCP server (used by Verizon FiOS) so I stayed with ISC DHCP server.
Further more, despite disabling DHCP in systemd, this systemd continued to spew network packets (think aggregate link and bridging).
Since I want no part of systemd accessing the network, I found that there is no way to QUIET that systemd despite its own config effort.
Not even Linux firewall can block this PID 1 (systemd).
Coupled that with recent but devastating CVE vulnerability of systemd, I’ve since moved to Denuvan distro, which uses SysV init as well as Debian APT repositories.
Initial pre-production review shows that this OpenBSD OS remains the only one OS that can block by PID.
So, I am sold.
No more effort to super-hardening of Linux. No more.
Just install and go.
- nix23 6y agoWhen fanboys kick you butt...welcome to HN ;)
- egberts1 6y agoYeah, ugly truth prevails.
- nix23 6y agoI just wait for the day when systemd implement's THE standard filesystem with a backup program a backup-status-webpage just viewable with their systemd-fork of webkit and presented with a webserver running with pid 1 (can even be used as a bootloader)...like that genius idea...journald.
- egberts1 6y agocan’t even Nagios (or any Network Management System access) into those journalctl-formatted file.
- nix23 6y agoIt's a stupid binary format..you have to convert it internally to a syslog'ish format which is clear-text readable even by humans and utilities like more...linux nih sickness once again, reinvent the wheel but this time we make it square.