Re:Fear and Loathing in Linux, or Who Needs /etc/motd (2010)
by dredmorbius on Monday August 08, 2016 @07:43PM
(#12251577)
1. Take something with an established functionality, that works, at least to some order (I'm aware of the debates on this concerning systemd).
2. Replace it. Without apparent option. In the /etc/motd case, the problem was one of swapping a read file with a dynamic process in more-or-less the same namespace. Systemd at least advertises its malevolence.
3. Fail to adequately document behaviours.
4. Deprecate bug reports.
5. Create a fragile system within a core system context (login(1), init(8)).
2. Replace it. Without apparent option. In the /etc/motd case, the problem was one of swapping a read file with a dynamic process in more-or-less the same namespace. Systemd at least advertises its malevolence.
3. Fail to adequately document behaviours.
4. Deprecate bug reports.
5. Create a fragile system within a core system context (login(1), init(8)).
Rinse, wash, repeat, rofl, weep.