You Got Your Windows In My Linux

snydeq writes: Ultimately, the schism over systemd could lead to a separation of desktop and server distros, or Linux server admins moving to FreeBSD, writes Deep End's Paul Venezia. "Although there are those who think the systemd debate has been decided in favor of systemd, the exceedingly loud protests on message boards, forums, and the posts I wrote over the past two weeks would indicate otherwise. I've seen many declarations of victory for systemd, now that Red Hat has forced it into the enterprise with the release of RHEL 7. I don't think it's that easy. ... Go ahead, kids, spackle over all of that unsightly runlevel stuff. Paint over init and cron, pam and login. Put all of that into PID1 along with dbus. Make it all pretty and whisper sweet nothings about how it's all taken care of and you won't have to read a manual or learn any silly command-line stuff. Tune your distribution for desktop workloads. Go reinvent Windows."

Comments

Troll much?

[Zero__Kelvin]

". Go ahead, kids, spackle over all of that unsightly runlevel stuff. Paint over init and cron, pam and login. Put all of that into PID1 along with dbus. ... Tune your distribution for desktop workloads. Go reinvent Windows."

Posting this uninformed drivel as a valid submission is a new low for Slashdot. Init runs as PID 1. Systemd runs as PID 1. In other words systemd renames Init to systemd. Does this idiot not get that systemd is essentially just a powerful universal init system that beats SysV and BSD style init?

Hint: A bunch of people still think Windows is great. Claiming that "lots of people don't like systemd equates to anything other than lots of people don't understand systemd, but will complain anyway is just stupid. Systemd works great, and most of the major distributions have chosen to switch to it for good reason.

Some people don't like them new fangled fuel injectors and still think a carburetor is the way to go as well. For those people, the old init systems are still available, but fighting progress with FUD is the Microsoft way, and while nobody is reinventing Windows here, these "systemd suxors" idiots are becoming the new FUD machine.

Re:What's wrong with Windows Server?

[Zero__Kelvin]

"Ignoring the very real problem that putting so damn much in PID 1 is dangerous for system stability and security"

Yeah. We ignore that because that isn't remotely true, and you are just repeating misinformation you heard and showing that you don't have a basic understanding of how Linux or systemd works.

"Also, despite the fact that dependencies are baked-in to systemd, it's not at all uncommon for a service that depends on an something else (service, NFS mount, etc.) to still start up before the dependency is fully ready, simply because the default systemd is to assume the dependency is fulfilled as soon as whatever "starts" it returns."

So it is not at all uncommon for people to use the default when they shouldn't, and that is somehow systemd's fault?

Re: What's wrong with Windows Server?

[phantomfive]

While the potential is there, we have not seen anything as bad as the OpenSSL bug.

Wow, go look through a vulnerability list some time