> It's essentially redoing the traditional Linux approach
It seems like that's part of their mission statement, given comments like this: "Some day, we will have turned the old crap into a real operating system. :)" -- Kay Sievers (https://plus.google.com/+TomGundersen/posts/eztZWbwmxM8)
Yeah, and they seem to be using Windows as their model of what a "real operating system" looks like.
Re:Systemd redux: The end of Linux
by lucian1900 on Friday November 21, 2014 @05:17AM
(#8640617)
Both Windows and OS X have a unified management mechanism.
In fact, OS X's launchd was a direct inspiration for systemd because of how nicely it works there. I've wanted launchd on servers for so many years.
OSX is not an appropriate choice for a server, and Windows has limited reputation in my mind since they put the GUI in kernel space.
we should not emulate the things we've overtaken and have a higher server market share than. Something we've been doing before is doing it right, and I believe it's the ability to be dynamic and modular.
Re:Systemd redux: The end of Linux
by lucian1900 on Friday November 21, 2014 @09:03AM
(#8641268)
Windows is actually used on servers quite a bit, but that's besides the point.
Service management has been a problem on (Linux) servers for a long time. Just because launchd originates on a desktop doesn't mean it's not a good idea.
To be clear, I'm not claiming that SysV init is The Best Way. Shell scripts are not the Happiest Place. But I am claiming that systemd is a crummy and overbearing replacement.