Fair enough, but applying a reasonable degree of reading comprehension instead of just skimming key words before replying is normally assumed.

Sometimes it turns up on servers with a relatively lean RHEL/Centos install and starts running when you don't even have X going - I have killed it on servers when they were running short on memory.

As an aside, a really weird side effect of pulseaudio is that if you block the port it uses it can really speed up remote X - got no idea what Lennart was thinking with that bug/feature. It's things like that which make me wonder why he's being allowed near an init system.

I used system V init on embedded system since late 1990 and I just delivered my first system using systemd this week.

You are a brave man to go in blind. I've been using systemd stuff on test boxes for more than six months and I've seen and worked around far too many fuckups to want to use it on an important production system, but at least I'm prepared to do some workarounds if I actually do.

Since some of them in high positions have been working a lot less time than Slashdot has been around that is far less of a joke than you think.

You say that, but why have nearly all distros moved to systemd?

RedHat staffroom politics and Gnome club politics. It's addressing the non-problem of a bunch of things being under the control of a lot of different people instead of just under Lennart's control. The "faster boot" never happened and was never a big deal outside of systems too small to sanely consider systemd anyway - the old init not doing much is faster than starting the systemd "cathedral" to not do much.

I complained about that on an earlier systemd article - the official fanboy response seems to be that because Lennart didn't write it ZFS on linux sucks while systemd is wonderful despite not working properly yet.
So I went back to RHEL6 and an init system that's been tested enough before release.
My home system is a recent Fedora - I just gave up and I've been starting ZFS from the command line on login after about the third change where systemd went from being able to start ZFS to not.

It's a moving target, so you can know what systemd wants this month but it's not the same six months later.

The above can really just be summed up as "it wasn't all a single project, but it is now with systemd". Progress certainly did happen before systemd started and there was no actual problem to be solved like there was with pulseaudio or NetworkManager (the old system was clunky with laptops - of course the new one now sucks with everything else).

PERHAPS someone could define what was broken so badly in init that the whole lot was replaced. I so dearly would like to know.

Apparently not enough of linux userspace had Lennart's name on it.
It's being widely adopted because he's convinced a few gnome people to make their stuff rely on it and the gnome stuff is popular.
I really don't know what RedHat was thinking when they put someone who thought it would be a nice joke to call a frequently running process "rtkit" in a position of responsibility.

So basically you'd be streaming your criminal activity on YouTube all the time? Because that would be stupid.

Sometimes deliberate jokes are deliberately stupid.

You seem awfully thin skinned in your denial of the obvious with some pretty fucking extreme edge cases.
Yes it's nice pretending the people beg because they want to and not because they have fallen through the gaps in society so that nobody gives a shit if they live or die, but it's not a very realistic way of looking at the world is it? If there are a lot of them about it's a symptom that somebody running the place has seriously fucked things up. Is your denial a pretence that your political team has created a perfect society?

No, they weren't in that state the entire time - the results of real experiments don't correspond with that, or with "hidden variables".

It's complicated, but the Wikipedia article on http://en.wikipedia.org/wiki/B... seems like a good place to start.

if I had mod points, I'd mod you as troll.

its not the 'basement dwellers' - those guys have zero experience in unix, given that they are alive less than 20 years, usually, and they know only what they've learned during the obama years and not much before that.

the rest of us who have used and managed unix since the 80's have to dump WHAT WORKED WELL and move to some new shit that clearly has issues, does not fit in or belong very well and is being forced on us.

see, the value of a craftsman is in his knowledge and experience of his tools. some people spend decades learning how to use their tools and work in their trade and the time shows; experience is worth having and paying for!

what happened now: some newbie decided the old way was not good enough and decided to change it all out, for no good reason at all (I have not yet seen a good reason to reinvent a wheel that has been working for longer than most of you have been ALIVE). faster startup is not a reason; this isn't a media player and linux still does not startup in 3 seconds or less, so what's the point of 'faster startup' when its really not fast enough to justify this forklift upgrade of sorts?

basically, the linux distros have been 'google-fucked'. I use that term to mean that some young snotnose didn't have anything better to do with his time and decided to royally break things and redo them, just because he thought it was a 'good idea'. but clearly didn't think it all the way thru and just wanted it because he just wanted it! typical google style; break things and trash all the old history of how things WERE done because, well, we just CANT LEAVE WORKING THINGS ALONE!

Yep, all of them live in nice houses just like this cancer woman cured it all with her diet. All completely proven.
Now where is that bridge I can sell to you.

Hmm, I often wonder if it shouldn't be changed to include the word "both" between "bear" and "arms".