Re:Don't panic and keep forking Debian
by cpncrunch on Friday November 28, 2014 @09:04PM
(#8672836)
I haven't used systemd yet, but I'm concerned about having to learn a completely new way of doing things. I manage a number of servers, and it would be a huge inconvenience figuring out systemd. The old way works fine for me. Unfortunately most of the servers I work with are CentOS, and it seems Redhat has switched to systemd so I'm not entirely sure what I'll do in future. I guess now I have another option.
[ Parent
| on HN ]
Re:Don't panic and keep forking Debian
by GFK_of_xmaspast on Friday November 28, 2014 @09:27PM
(#8672879)
"I'm concerned about having to learn a completely new way of doing things."
That's just a fact of life in this industry tho.
Yes, of course. I occasionally learn a new language (or develop one), and I'm regularly using new APIs. However this completely changes everything about managing servers, for no compelling reason. It will create a large amount of hassle for no significant benefit.
No compelling reason? you should probably read the docs a bit more. If you don't have any philosophical concerns with systemd, then you will find a lot to love there.
I just re-read some docs, and I still can't see any compelling reasons. I'm not concerned about booting a few seconds faster (I only reboot my servers once every year at most). Regarding memory footprint: that has never been an issue. Binary logfiles are a disadvantage to me.
Binary logs and the amount of new code which these developers are incorrectly assuming will be stable. It is a total disaster in my opinion. I fell in love with using Linux because everything is text files. Binary approaches will only make using linux more cryptic.