In Oregon, it's "Stop if you can". You are to treat the yellow light as a red light unless it is unsafe to stop.

And this would not be an issue if he wasn't an arrogant person who treats systemd like his own personal playground.

Back to my point. His Google+ nick says everything that needs to be said about his management style.

No real need to assassinate that which is already dead.

I'm sure he's a just fine person, who has no intention of ever listening to anyone who might know a better way.

Just as an aside, have you noticed that his Google+ username is LennartPoetteringTheOneAndOnly?

This says pretty much everything that needs to be said regarding his mindset. To your point.

That's one FS I think the linux world could, at the moment, do without. It's got some cool features, but is not ready for primetime.

If you read one of the last comments, they appear to have listened and are considering reconsidering this decision.

Which marks the difference between a professional development shop such as Google, and Lennart Poettering.

User requirement.

In fairness, I installed Ubuntu *server*. I'd expect it to behave like a server, not a spin of the desktop distribution.

Sometimes you use what the user demands/needs rather than what is the best choice technically. I'm not too fond of Ubuntu on the server either, but there are specific reasons for it in our particular environment that I can't get around.

If there was a way to package an already built gentoo distribution for rollout, I would seriously consider it. (and there may be, I haven't used Gentoo in a long while)

It's not an option for the huge company I work for, though. Most companies want Debian or RPM based systems.

I was using it as an example to show that server workloads are fundamentally different from desktop workloads.

Where did you get the idea that this was about forking the kernel?

Linux (at least in this context) is not only the kernel, it's the whole ecosystem - whatever you call it. I don't think the person who wrote this article was arguing that the kernel should be forked. The only time I'll seriously consider that is if they try to put dbus into it.

I don't see anything wrong with the kernel that a little tuning can't fix. I do see plenty wrong with lots of distributions.

I am a linux sysadmin, and many of the packages required for desktop use not only don't apply to me, but are pretty well useless. I would love to see a distribution where any dependency on X11 was not only stripped out - but *compiled* out. I would love to see a distribution where systemd was not getting its mitts into everything.

But it's not only that, it's tuning. I discovered that Ubuntu's default scheduler settings on a Dell R620 with 384G of RAM and a nice beefy RAID 10 array are actually the *worst* settings for this kind of system. Everything else I tried - other schedulers, tuning CFQ, etc., they all led to better write throughput. Which leads me to wonder how many processor and other cycles are wasted because sysadmins just install with the default settings and hope for the best?

There needs to be a distro where the adults are in charge. I'd even build it if I had time, and I most certainly would be willing to put some time into working on one.

I completely disagree with you. Particularly the last sentence, which, again, is coming close to an ad hominem. I didn't make that argument and I wasn't going to.

I don't upload photos that I don't want distributed widely to iCloud. I figure if I do that I'm just asking for whatever happens. And that is the way *I* look at it when it comes to my own business, so I won't listen to anyone telling me I'm wrong.

I'm done here. One can never win this kind of argument because there is never any rationality to it. It's all emotional.

Indeed. This is not zero-sum. Just because a bad actor does something reprehensible does not mean that there is not an opportunity for education on how to reduce your risk. Don't crack. And don't put yourself in a situation where it's likely you will *be* cracked.