On Tue, Oct 14, 2014 at 10:55:33PM +1100, Chris Samuel wrote:
I'm curious after the recent storm about systemd to find out how many people have actually tried to use it?
i've got it running on a laptop. as init, it seems to do what it's supposed to do. it doesn't do anything remarkable that's worth the overly tight integration of lots of other programs. every few upgrades i have to fight it to force it to disable some new shit that it has borged that i don't want it to do. i don't want it handling ntp or logging or dhcp or anything else - all i want init to do is init. if systemd limited itself to just init then i wouldn't care much whether i was running it or sysvinit or upstart or openrc, the differences just aren't important enough to give a damn about. it's the fact that systemd tries to do so many other completely unrelated things that make it a menace. anyway, the experience has been enough to make me determined to keep systemd off my main systems for as long as possible (hopefully forever, but that's unlikely due to systemd's creeping featuritis and the growing number of direct and indirect dependencies on systemd) systemd's sudden surprise takeover of power management resulted in it shutting down the laptop during an upgrade (remote via ssh while the lid was closed). it took me ages to figure out what the culprit was and to fix it by adding "HandleLidSwitch=ignore" to /etc/systemd/logind.conf. and then it happened again during another upgrade when logind.conf was replaced and systemd reloaded. that kind of dumb shit was fixed for, e.g., upgrades of sshd way back in the mid 90s (when upgrades of sshd could result in your ssh session dying and no ssh daemon running, leaving no way to login and finish the upgrade - i used to have to keep telnetd-ssl running just to work around that)....but learning from history is beneath the systemd developers. craig -- craig sanders <cas@taz.net.au>