Poettering's standard reaction to something breaking because of changes introduced by systemd seem to be akin to Jobs and antennagate, "you are doing/holding it wrong".

Ran into a email a few days ago in relation to systemd trampling libvirt cgroup configs. It could basically summarized to "libvirt needs to supplicant itself before systemd".

It is the same kind of ivory tower attitude as we could see back when systemd would DOS the kernel if the kernel command line contained the debug flag.

In Poettering's world you don't diagnose, you just restart and keep on trucking. It is uptime by machinegun devops.

The main devs on systemd seems to be coming out of a combo of devops/cloud and desktop, with little to no regard for keeping serious servers up for years on end.

In essence their idea of uptime is more akin to machinegun fire. Dump everything into containers/VMs, and just fire up a new one when the old one goes belly up. Don't care about bugs etc, just restart restart restart.

Not just feature requests. They are bluntly stated that any patches for functionality they have no interested in will be rejected.

Damn it, they even yanked HDD readahead support recently because everyone on the dev team was using SSDs.

It's like Torvalds yanking everything out of the kernel that didn't support x86 because thats all he is running on his desk.

Why oh why is it that the naysayers are the ones that has to move on and start over?!

Why could not Poettering and CO create their own distro and prove it functional from the ground up first?!

Damn it, look at how it is done at the kernel. New subsystems are maintained outside of the main tree for years while the bugs etc are hammered out.

Poettering and crew is not just replacing init with systemd, they are replacing everything between the kernel and the web browser with something new. This should really require that it is developed in isolation until the feature creep has come to a halt, and the bugs can be found and hammered out.

The latest changes include stuff like ADSL controls in networkd and folding power management into logind.

It barely makes sense that this has found its way into virtual noname distros and such. But that RH and Canonical is putting them into releases is whacko.

So in essence the "wise" men of Gnome took the already questionable gconf, that used XML files, and turned it into the binary files based dconf...

Fuck it, i'm going back to XFWM...

How long before they have to replace anything beyond the GNU stuff with something out of the 90s to avoid dragging in the systemd shoggoth via some dependency or other?

The only behavior systemd "expects" is for daemons to talk to it either via dbus or libsystemd.

http://ewontfix.com/15/

Everything else have some kind of problem attach that is just waiting for the admin to tun his back on the rack.

LAMP offered a way to rapidly spin up a .com on commodity hardware that could then woo the VC.

Kernel devs have in the past and will in the future (at least as long as Torvalds is in charge, and i fear the day he retires) keep sub-systems and such in the code if they know there are users of it out there.

Damn it, even though everyone says that you should use the ip command for anything network related, ifconfig still works. This because the interfaces between the program and the kernel is still there, after having been labeled "depreciated" for a decade or more.

A basic operating rule for Linux kernel developers is "do not break user space!".

Best i can tell, because it take into account the whole USB address tree when linking a device to a driver.

For me there is a line between cheating on a single player game for my own amusement (poking at ram values in a console emulator for instance) and automating online play against others.

In the first instance, the only one that is potentially hurt is me. This in that i may ruin my enjoyment of a game.

In the second i am ruining the fun of everyone that share the server with me.

Yeah, nofail. Thats up there with their abuse of debug in the kernel command line.

nofail is simply about supressing the error message on a failed mount, nothing more, nothing less.

Have the whole system go into panic mode because of a vestigial USB mount is missing is not sane by a long shot.

When the issue was raised to them enough for Poettering to take notice, their "solution" was a default timeout on every service for both bootup and shotdown.

This then blew up the following Fedora alpha, because they had a service that ran on first reboot after a system update that ended up taking long enough to tripped said timeout...

Their overall development methodology seem more at home with a website than a central OS component.

Iirc, systemd no longer optimize for "spinning rust" as the major devs have all moved to SSD...