On 9/10/2014 1:44 PM, Russell Coker wrote:
systemd is a debacle, good luck making it workable for yourself and others whom believe it is the /right/ way forward irregardless to popular opinion of most users -- including the silenced [moderated posts? thread] majority whom care like myself.
Install it and it just works.
For some, not for everyone -- that's why you are still trying to make it work by your own admission???
The only problem I've seen with systemd is the journal file being excessively fragmented on BTRFS. As you don't use BTRFS that won't be an issue for you, but if you did then you could just configure systemd to limit the size of it's journal (which is a good idea anyway).
I've heard of one case where an auto-mount USB device that wasn't connected at boot time caused systemd to fail to boot the OS, even though the file system on the USB device wasn't significant for the boot process at all. There are more systemd issues, but most of all, the so called ills of sysvinit are due to poor [errors] configuration and not a failing of sysvinit itself. People often mocked Debian for being stale for the stable installations ... give me stale with sysvinit any day, it works very well -- don't force packages to depend on systemd, it is not wanted, nor warranted; fix any apparent configuration issues [that's all they of the issues that exist] with sysvinit and you don't have any need for systemd. Upstream, for gnome and network-manager, well they need to remove reliance on systemd and fix their own issues relating to configuration with sysvinit. A.