Originally posted by Pawlerson
View Post
I've NEVER had dhcp issues with Linux running SysV init. I've had it over-and-over with a systemd linux. And sorry, if the Linux is "ready to go Out-of-the-Box", supposedly - I stop caring if the issue is in systemd or dhcpd. Nor I care about trying to fix it. Especially considering how fucking difficult is to debug anything about this pile of binaries systemd is.
I know about advantages but systemd advantages. But who is the target: sysadmin. I'll grant, it makes admins job easier and does not require as deep knowledge in scripting any longer. No longer have need to build same functionality using custom shell scripts. Desktop-user has little use for systemd but has to fight with the bugs all the same. And Poettering by proven personal characteristic, does not give rats ass about bugs either - unless some bug is really a game-breaker.
Ages a go, ability to do it with shell scripts was considered big advantage for sysv init - because you could do anything like this, guess times have changed. Admins of coming generations have less in-depth knowledge or something.
Originally posted by Pawlerson
View Post
There really is no choice but to use it, since it's collectively being shoved down by everyone's throats. People who are really unhappy with systemd have already migrated over to BSD or stuck with one of the few Linux distros not using it.
Shoved down -> not using systemd takes distinctive effort working around it for distributor. This is probably the one of the reasons so many distros went with it, it means less work.
Comment