Slashdot Mirror
Linux Mint Will Continue To Provide Both Systemd and Upstart
jones_supa writes: After Debian adopted systemd, many other Linux distributions based on that operating system made the switch as well. Ubuntu has already rolled out systemd in 15.04, but Linux Mint is providing dual options for users. The Ubuntu transition was surprisingly painless, and no one really put up a fight, but the Linux Mint team chose the middle ground. The Mint developers consider that the project needs to still wait for systemd to become more stable and mature, before it will be the default and only option.
The reason that "nobody put up a fight" is because every intelligent Linux user has seen systemd for the disaster that it is, and they've moved to FreeBSD, PC-BSD, OpenBSD, NetBSD or DragonFly BSD months ago. The only Linux users left are the ones who'd be just as happy using Windows, which is pretty much what they get when using a modern GNU/Systemd/Linux distro.
Precisely. I can't get that everyone and his dog is rolling over and playing dead with this. They *ALL* remember what came of all of Lennart's OTHER projects. Stuff looking for problems to realistically solve. Stuff that's still not QUITE "right" and the man, rather than finishing the job, moves on to the next disaster. This is no different. This has no place in a "mission critical" space- and yet they're letting them do it. I question the sanity of Red Hat in bankrolling this travesty and then jamming it down our throats in the FIRST damn place. Just like with PulseAudio. No compelling anything, really, and the proponents keep thinking that network service on this little userland mixer feature (which should've been a service of the DRIVER layer for one piece, the mixer) is the greatest thing- when it's part of the latency problems with sound. First hint it's stupid...Android doesn't use it.
As someone who has spent the last week plus upgrading his server to Jessie, I completely disagree that the pain isn't in the switch. It may very well be that more pain is coming but the switch itself has been quite painful and isn't over yet. How the fuck do you do a meaningful Google search on "systemd complains that starting Apache fails and shows the service as stopped but the process actually starts and Apache is working just fine, systemd apparently just doesn't know it?"
I'm on ubuntu 14.04 and a few times now, systemd of some kind (udev, I think) went cpu bound on me. my fan started spinning like crazy. kill -9 fixed that (the systemd proc). afaict, nothing else went wrong after I killed that proc.
its still not ready for production use. give it 2 years AT LEAST. if I was sysadmin at a place that needed reliable linux, I'd stay back on a non-sysd system for about that long, if not longer.
--
"It is now safe to switch off your computer."
The summary (and the article it links to) have the situation backward. Ubuntu is the distribution which is offering users the coice of booting using Upstart or systemd. Under Ubuntu you can currently chose which init software to use (as of Ubuntu 15.04). Linux Mint does not do this, at least not yet.
Linux Mint has two primary branches, Linux Mint Main (which uses Upstart for init) and Linux Mint Debian Edition (which uses SysV Init). Which each branch you get just one init technology, you don'tget to choose which one you want. This is largely becaue Linux Mint Main is based on an older version of Ubuntu (Ubuntu 14.04) and was released before Ubuntu started offering two init systems.
Let me just point out, Oracle Linux 7 is systemd only. Oracle switched Jul 23, 2014. So yet another enterprise vendor that doesn't buy into the whole "systemd isn't mission critical ready" meme you all are pushing.
The issue is not with systemd corrupting the binary logs, or with the filesystem corrupting the binary logs, but with the fact that they are -binary- logs. A log file should be an ordinary text file. Nothing more, nothing less.
To say nothing about the very concept of systemd being a BAD IDEA. One daemon to rule them all and in the darkness bind them? Give me a break. It used to be that Linux was a fairly faithful UNIX-like operating system. And you know what makes a good UNIX or UNIX-like operating system? The tools, specifically those that are well-written and do one thing and do it well (with reasonable exceptions). Systemd is neither well-written nor does it do one single thing very well, well maybe corrupt your log files and crash very, very spectacularly.
By the way, if you're so worried about your filesystem getting corrupted, why use ext4 at all? It contains serious design and implementation flaws, specifically concerning the journal. XFS is by far a better journalled filesystem, with none of those issues. It is simply the best choice, especially if your concerned with the integrity of your data.
And on the Eighth Day, Man created God.