Slashdot Mirror
Debian Technical Committee Votes For Systemd Over Upstart
sfcrazy writes "Bdale Garbee,chairman of the Debian Technical Committee, called for a ballot from the TC to chose the default init system. The votes are in systemd is the clear winner here. Bdale himself voted for systemd."
the default init system for Linux architectures in jessie
Having been a well behaved, not overly vocal member of the slashdot community for many years (10? more?), today, I found myself banned by ip. and my Karma (which has always been neutral) reduced to "terrible".
I had posted 10 times over the last 48 hrs, in support of the slashdot boycott. Most sensible debate, some houmour.
You know once the powers that be need to silence those who gently disapprove, that it's all gone terribly wrong, and those pushing for change that damages everyone are too weak to even make a sensible argument.
Oh Dear.
It's a shame to see a bunch of Canonical shills on the Debian Technical Committee though. This should have been strictly between OpenRC and systemd, but the Canonical shills were trying to push Upstart even though it's a buggy piece of shit that is inferior to systemd in every way.
But no worse than systemd, which is near universally despised by system administrators.
Does slashdot have Leonart Poettering on the design team, by any chance? It would sure explain a lot.
...here.
Finding God in a Dog
I didn't really know much about systemd being a ubuntu user, but found this giving more background on the story: https://wiki.debian.org/Debate.... The wiki does a good job detailing the technologies. Given the information, the choice of systemd is interesting.
Obviously, there's been a big push across the board by many various distros, but what are the real benefits of systemd? Is it better for average end-users (Easier? Faster?) or those more technically inclined (more stable, uses less resources, more configurable)? Or is this simply a case of it just being non-Canonical?
Who would have thought there would be consequences to spamming every article with whining and bitching?
Justice is served. Keep up the bans and let's get rid of the deadwood.
I fully support the rights of a bar to throw out the belligerently drunk - that's not censorship, it's called caring for your customers. None of us are here to read moronic posts about website style changes. We are here to read insightful commentary on technical stories and if you can't handle that, you do not and should not belong.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Or, the CLAs are the Slashdot Beta of OSS Communities?
I do not know, just keeping the flame alive... ;-)
*** Suerte a todos y Feliz dia!
I don't think I have much qualm about systemd as it relates to the init process. However, the people behind systemd push *hard* that text format logging is some anachronistic evil and that files on disk should just be binary. They do some pandering to the crowd by saying to run something like rsyslog alongside systemd, but that seems pretty counter to the other areas where there is an emphasis on running as few processes as possible (ambition to replace at, cron, change from running static number of getty on VC specified by inittab to on demand spawning of getty as auto detected). It's clear they regard users valuing plain text data with some disdain. There is plenty of opportunity to achieve the gains whilst concurrently providing a plain text stream to peruse natively, but they have *zero* interest in trying to pursue such paths.
This is also the brainchild of Lennart Poettering, who has had a track record of getting stuff widely into distribution critical usage path before it's ready (avahi and pulseaudio have given me lots of headaches). Also trying to get DBus into the kernel, which seems absolutely bonkers.
In general, distributions embracing this become increasingly opaque to admins. Distribution behavior flows through an increasingly complex labyrinth of crap that it approaches Microsoft level BS. I'm somewhat disheartened at the possibilities here.
XML is like violence. If it doesn't solve the problem, use more.
FWIW, having worked with all but OpenRC - I very much like the approach of systemd's small interpret-able/generable files.
I get the flexiblity of external support scripts when I really need them, but 9/10, defining the dependencies well avoids the need for any scripting at all.
At scale of more than a few dozen machines (and especially when they're coming and going), this is amazingly powerful - one set of tools can write them, another can read them / interact with them via DBUS, all while managing most every aspect of the underlying process in a single well documented way (the manpages are /awesome/)
you mean canonical has something else than alpha builds of some sw??
world was created 5 seconds before this post as it is.
Ubuntu used to be good before they destroyed themselves around 2011.
Mint is an Ubuntu fork after all...
No, it is loathed by a small, vocal, percentage of system administrators, who have very little in the way of technical arguments at their disposal. This vote may be considered evidence in that respect.
There is very little to recommend init scripts. I dismiss arguments that they are any easier for any average mortal to deal with than any other piece of code, and there is very little justification for wasting CPU time on a non-interactive process. Additionally, this will merely be a default -- those who want slow boots, or think cgroups are evil, can go ahead and install systemv-init and purge systemd. Or, since systemd, d-bus, pulseaudio, and wayland are evidently the future of Linux, the malcontents can install BSD -- it comes with a free chip for your other shoulder.
Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
Their recent updates have broken udev so badly, that Gentoo decided to fork udev to retain the old design. Debian should pay attention.
Yyyeah, no, I heard a lot of hate for it, but Oh god, upstart is a disaster. It's a dependency-based system that doesn't do anything with its dependencies! Systemd's a little bit terrifying, but it actually does the job it sets out to do, while every time I sit down with upstart I wish I was just using basic sysV+LSB init.
You do know your pretty flagrant racism makes your opinions automatically much less sound, right?
Upstart was unnecessary in Ubuntu. Systemd is not necessary in Fedora or Debian.
There are other ways to get fast boots, without create another monolithic do-everything daemon with spaghetti dependencies.
Basic software engineering principles (and Unix principles), should tell you that do-everything daemons, like upstart, systemd, hald are bad ideas.
With such complex, unmodular core Linux systems, Linux based OS's will grow increasingly more unstable and insecure.
Also, systemd and upstart make Linux much less suitable for embedded systems.
The choices, I guess, are:
Fork the pre-systemd Debian. ... Android.
Start fresh, perhaps even starting with the simple event based init system from the most popular Linux distribution in the world
A lot of whining, but no actual arguments. May you have the kindness to give reasons for your aversion to systemd before insulting people?
Interesting...I prefer systemd over upstart and I know many others that do as well. So I know it is BS to day systemd is almost universally despised. At worst it is seen as the least of all evils.
It anything the debate is over retaining init.d scripts and systemd as upstart is somewhat of a single vendor stepchild. The main legitimate concern with systemd is its Linux-only implementation complicating the porting of packages to BSD and HURD based systems. The other might be a matter of taste but still worthy of debate--that systemd does not honour the 'Unix way' sufficiently.
This is good because it will get systemd onto even more systems, which will hopefully be a forcing function for improving it so that it's more usable.
The introduction of systemd into my distros of choice (I was a heavy Arch Linux user until this year, when I switched back to Fedora after a ~8 year absence) has caused me more problems that any other single change to any part of the Linux operating system in my history of its usage (and I've been using Linux since 1994).
I'm at the point in my life where I just want things to work; and I found that systemd has in many places not worked well. I wholly believe that the problems are generally due to the implementation of the individual services, and not bugs in systemd itself, although I suspect that the 90 degree turn taken by systemd and its associated complexity are the genesis of the problems in the individual services themselves.
In particular, I've found that systemd on Fedora cannot properly start up an NFS server. I have a post-start up script that I run manually to start NFS because no matter what I do, it does not seem possible to force systemd to start all of the requisite NFS services. systemds tools for figuring out what could be going wrong are, I am sure, complete, but very impenetrable to a person who wants to understand the minimum necessary to fix a problem.
Additionally, it seems to be easy to break systemd's boot scripts in a way that prevent systemd from being able to boot the system (it's happened to me over and over again through what seemd like innocuous user actions), and I have never successfully gotten systemd to boot into its recovery shell. I can get to the recovery shell but I can never type anything into it, it seems like there's something borked with the way it handles keyboard input somehow.
In summary, systemd is much less mature than init ever was, which, combined with its tendency to reimplement everything and thus de-evolve much of what used-to-work into no-longer-works-easily, has resulted in whole system failures at a rate that I have never, ever experienced before under Linux.
All that being said, it's pretty clear that lots of Linux distro maintainers are more excited by the few advancements that systemd makes over the old init system, than they are put off by the lack of maturity and quality of systemd; therefore, systemd is an inevitability, and I'm glad that debian is taking it now, because it will mean even more developer effort towards fixing its problems.
In short: more pain for other people, making them more likely to fix my problems for me. So I'm happy that debian is doing this to their users, for my benefit.
honestly, i would rather have something that is known to work in the long term and not need update to patch bugs or possible changes to the config file implementation. let's just use something that we know works.
on the other hand, couldn't it be an optional package (a package is required but there are multiple to choose from) with the default as systemd?
Anons need not reply. Questions end with a question mark.
...is that "systemctl" is a lot of keys to type, and the last four are all consonants.
At least "service" is an actual word.
systemd is Roko's Basilisk.
Looks like the MS Embrace/Extend/Extinguish is reaching the End-Game since SystemD is exactly that. Who will pay the Piper in the future? Thankfully not I as I didn't call them in but now I'm down to a single Open Source OS - BSD as Linux has screwed the pooch.
Can't stand Apple and Sure as hell don't care for the crap called Win8. Guess I need to dive into BSD again and start learning how to use it.
Mod me up/Mod me down: I wont frown as I've no crown
For some reason I expected the next sentence to be "We could fight them with conventional weapons, but that could take years and cost millions of lives".
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
If your using this sites comment system to try and destroy this site with a boycott, why do you expect to have good karma on this site ?
Then why's mgt. here (rant removed) ?
That reponse pretty much explains why your karma is burnt and your posting anon. Your post is not relevent to the story or the comment you replied to.
Really? In my head I heard " we shall fight on the seas and oceans, we shall fight with growing confidence and growing strength in the air, we shall defend our island, whatever the cost may be. We shall fight on the beaches, we shall fight on the landing grounds, we shall fight in the fields and in the streets, we shall fight in the hills; we shall never surrender"
Followed of course by the first bars of Iron Maiden's "Aces High".
ACs don't waste your time replying, your posts are never seen by me.
...The problem is that systemd is too opaque, much like Windows "you don't get to see" philosophy. It's contrary to the way Unix based OSs have always been.
The people who are so desperate for a Windows-like OS should just... use Windows! Windows more or less works fine if that's your cup of tea.
This bears repeating, so I have repeated it. Systemd is philosophically Not The Unix Way. Microsoft has been doing things the systemd way for much longer than Poettering & Sievers, and is better at it.
I have no desire at all to use an ersatz Windows. Which is probably why I'm using the real thing more than I am using Linux these days. Not happy.
When is the last time you hand configured your monitor, putting in desired refresh rate, etc.?
I'm not convinced that this is a good move, but I'm also not convinced it's a bad one. I don't know. It's beyond my area of expertise.
FWIW, I don't understand why the init process needs to be changed. My feeling is pretty much "It ain't broke, so don't fix it.", but there may be valid reasons. Two different groups of people seem to think so.
I think we've pushed this "anyone can grow up to be president" thing too far.
You'll need more than a shotgun if you head my way, punk.
And looking at your username, your shell won't help you a bit.
I couldn't care less that the protesting about beta has your panties in a knot.
We are fighting the change to beta with the tools available to us. If you don't want to be in the conflict, just leave....no one is stopping you.
If you are going to sink to physical threats, then I am your Huckleberry, bring it on if you are more than talk. I'm in Oklahoma, and posted my address prior on /. if you are serious, otherwise you can STFU, IMO.
I'm also off work recuperating from a surgery, so time and schedules are not a limiting factor. Come on! I'll even give you a handicap: I ONLY get to use my issued Ka-Bar!(that's an indication of how much of a threat you really are)
BTW, you could use a LOT of work/education on your insult/name-calling skills, as they are currently presented, they're pretty lame. ;-)
Down With Slashdot BETA!!! I've been around the corner and seen the oliphant; you can only abuse me from your perspecti
Yes, yes, Gnome3 depends on logind/systemd. Also ConsoleKit ceased development. It's almost as if they think it's a better technology. But hey, you want to install a massive monolithic DE, it's gonna pull in some dependencies that you may or may not like. That is not Debian's problem, actually -- if they showed any signs of being amenable to discussion on the matter, then you might complain to the Gnome developers.
This vote ignored the issue of what kind of default the default should be, because it only had one question that was being decided. It is unlikely to be the end of the discussion on the matter, so I am sure that all those with opinions will get their fair say -- just not on this vote. I realize that the vote may not have gone your way, but those grapes were probably sour anyway.
Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
That said, if reports about window managers beginning to rely on systemd are valid, this may have been a foced move. I, personally, see no reason to move from sysvinit, but if KDE starts to perform poorly, because it's assuming that it can depend on systemd to supply some services....well, I'd be unhappy.
I think we've pushed this "anyone can grow up to be president" thing too far.
An earlier post by another proponent of OpenRC said that it was still too beta to be adopted, even though he regretted it.
I think we've pushed this "anyone can grow up to be president" thing too far.
I am not putting a convoluted, megalomaniac-spawned and KISS-violating atrocity like systemd on my systems. The binary log-format alone is a faux pas to severe as to invalidate the whole thing. Are there any good server-distros left that stay away from systemd or that are at least commited to maintaining a different init system longterm, preferably the classic SysV init?
Of course systemd will fail eventually (once enough people realize it is a bad clone of what Windows does and makes things worse, not better), but I am unwilling to wait that long or tolerate all the disadvantages this thing brings in the meantime.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
It is my understanding that the argument of substance in favor of systemd is not that it is a better init system per se, but that it is something fundamentally new: a flexible and powerful asynchronous actor on events.
If not good alternative presents itself, I may just rip it out myself and stay with SysV init. Boot-times are pretty irrelevant, especially for a server-distro like Debian.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
And that shows just how _wrong_ this all is. A GUI has no business in hell depending on an init-system. This is all very un-UNIX, KISS-violating, bloated, Windows-like. Why do so many people not see what incredible amount of things they are breaking with systemd?
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
I really hope Gentoo will stay away from making systemd mandatory. I now have a good reason to migrate there.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Linux is no longer Unix-like and is slowly turning into some sort of a Windows hybrid (RedHat and others) that will ultimately become the enemy of Unix. Terrible decision by Debian. Other Linux distros will follow suit and will most certainly become non-Unix more and more as time reveals their true intention.
I personally have tried a Mac. After 18 years of nearly Linux-exclusive computing, in 2012 I was wooed enough by the new retina Macbooks and tired enough of dealing with Linux suspend/resume/hibernate nightmares on laptops, that I decided to give a Mac a try.
Long story short: I like it, and nearly love it, but am disappointed in many aspects. The hardware is definitely a high point - I can honestly say that I have never owned another laptop with even close to the same quality of hardware design or manufacture as my 15 inch rMBP. And I say that despite having to return it to the store once to fix the image retention (at the same time getting a mainboard upgrade to fix the video flickering problem that was common on this laptop), again to fix the wireless that they somehow broke during the first fix, and finding that about 6 months later I killed 4 or 5 pixels on my own when a small grain of sand got onto the display and I closed it (the retina displays have literally *no* protection of the LCD surface and it is easy to pit/scratch them - my fault for taking the laptop on vacation I guess).
Mac OS X has impressed me with how well it integrates with its hardware, how nicely and seamlessly the UI functions, and how good the video drivers are. Also Apple's Objective C implementation and libraries are an interesting mix of weirdness and awesomeness, with the very best documentation I have ever read for any programming environment hands down (Microsoft's widows documentation is a complete and utter joke when compared to Linux man pages, let alone compared to the incredible documentation that Apple has for its APIs).
However - the Mac is still a let down in some areas. Printing is surprisingly difficult and bad. I am amazed that a company that created the desktop publishing market and that sold the first Laser printer, can have such an awful print dialog. It's inconsistent between apps and doesn't let me WYSIWYG the printouts whatsoever (I print alot of coloring pages for my kids and it's amazingly hard on the Mac, no matter what program I use, to get an image centered and fit to a page for printing). Also, some of the UI misbehaves sometimes - I've taken to completely disabling the wireless status icon in the menu bar because it tends to freeze up the entire menu bar functionality whenever it's searching for networks or otherwise unhappy. Which happens just about every time the laptop comes back from sleep.
Also I cannot stand the fact that Apple cannot give the user the choice of whether or not click-to-focus or focus-follows-mouse. Oh my god the number of times that I have been unable to interact with a program while looking at a web browser or somesuch because they overlap and I have to fidget and fuss with window positioning and size to be able to do my work. On any other system without this ridiculous flaw, I can type into my emacs buffer while observing some web page with documentation partially on top of some part of the emacs windows. But on Mac OS X I often just have to give up and copy-paste into a text edit window, save that to a file, and then open that within emacs because I just cannot manage to get the stupid windows to overlap in a way that lets me get what I need to do, done.
I think if Apple would not be such fascists about some UI policy, the Mac OS X experience would be alot better.
But overall, I'm like 90% happy with Mac OS X. Definitely beats the living hell out of Windows.
This site used to be great. Even in it's latter days, it's been good. That is poised to change. Before long, it will be mediocre, and ordinary.
I didn't see a problem when Dice Holdings initially bought Slashdot. I figured there would be efforts to drive nerd traffic towards their job listings and such. That was fine. We all need jobs.
Things have changed now. Beyond the shifts in story choices, the slashvertisements, and so on, something fundamental has changed: Slashdot's owners do not appreciate it.
Their recent financials show that they have written its value as an asset down to zero. They have legally claimed it to be worthless. That is at the root of what is happening now. They want to fundamentally change the nature of this site in order to remake it into something with big growth potential.
Beta is just the latest symptom of this disease. It will not be the last. In striving to make it into a site that will bring them a growing user base and growing revenue per user, they have shown a willingness to dumb down the interface in the name of making it more accessible to newcomers, to cast aside essential elements of decade-spanning community culture, and to plow ahead with changes in the face of overwhelmingly negative user feedback.
This is not going to change. This will not go away. I will not support it.
I will be gone for this entire week, in protest. While away, I will work to create a new community where things can be run with quality user discussions as the paramount objective.
Be seeing you.
I'm among the many who have built up a healthy aversion to certain software after having been repeatedly burned by Pulse. I would not have chosen systemd. That said, I have tremendous respect for the Debian team, and am optimistic that the worst of the problems we find with their choice will be addressed within a couple of years. Let's get the bickering out of our systems quickly, and move on to helping one another turn the new init into something genuinely good.
Wow, that sounds way simpler than just browsing the network share that is already visible from within dolphin, from within VLC's file-open dialog, like I do with every other platform!
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
We shall fight on the beaches, we shall fight on the landing grounds, we shall fight in the fields and in the streets, we shall fight in the hills; we shall never surrender"
So, just like my family vacations?
I'm a minority race. Save your vitriol for white people.
as a debian user i am puzzled by why this monstrosity was chosen instead of something that adheres to the 'do one thing and do it well' philosophy. why are we slowly turning gnu/linux into windows?
Zawinski's law: Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
i propose we include an email client functionality now and be done with this horrible one-thing-breaks-all thing.
Too beta in Debian. It's been used for years in Gentoo, but was only added to Debian's package archives a couple months ago.
read more about it at: http://ewontfix.com/14/
Gnome wants to allow admins to keep track of what different users are doing and enforce permissions and what not on their utilizeation of the system.
Sounds good right? They had policykit, but determined that logind did that task better. Logind ( part of systemd) just does a better job of doing that one job. It turns out that monitoring all the processes a user creates through using a desktop is a very simular task to the more general job of monitoring a daemon and all of its processes. So it makes sense to have the same tool perform very simular tasks.
So, if you don't understand what systemd does and what gnome needs, your statment makes a *lot* of sense. But when you figure out what everything does, it just looks wrong. Why re-invent the wheel for the same task? This *is* KISS. Re-inventing the wheel is not KISS, adds bloat, duplication of effort and bugs.
Well.. maybe. Or Maybe not. But Definitely not sort of.
If you think being a nerd is about doing things the most awkward ass-backward way possible, you're an idiot. Easy things shouldn't be difficult. Make easy things easy, and spend the time recovered on less pointless fuckwittery.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
It's not just boot time that is faster (it was just the most obvious). Even normal service starting/stopping and some logging stuff is faster. There are also some very powerful log querying you can, though I haven't really looked into them much myself.
Please elaborate.
I can't criticise personal choices. (It seems he has approximately the same problem with Ubuntu as he does with black or gay people though.)
Binary log files are Evil(tm). A single stray byte out of place and the log is destroyed. (never used checkpoint firewall, or innoDB I guess)
WSC would never have used a comma between the subject and its verb. That's the kind of thing Germans do.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Why didn't you list DOS 2? Oh yeah, because it was hugely popular (for its time), thanks to its support for hard drives with subdirectories. Not as widely deployed as DOS 3 would be, but far from a flop.
You're correct that DOS 4 flopped. That's one data point. (And really, that was IBM's failure, not Microsoft's.)
DOS 6 was widely adopted, replacing DOS 5 (which had little to recommend it except that it wasn't DOS 4) and living a long and productive life under the 16-bit versions of Windows.
Windows 98 enjoyed quite a bit of success, and (except for being a trojan for IE4) deservedly so; 98SE was the Windows that people stuck with on their older hardware rather than installing the resource-hogging Windows XP. Perhaps you were thinking of the deservedly-reviled Windows ME, which followed it?
You're also correct that Vista and Win8 have been flops. So that's three data points, but non-consecutive. Microsoft's success/failure pattern isn't quite as simple as you misremember.
http://alternatives.rzero.com/
Actually, I think it's partly the embedded people who are pushing for systemd. Which worries me, since many of them don't know or care about Unix.