That would be pretty neat. But until then, the world will continue to run on systemd, because it _works_.
That would be pretty neat. But until then, the world will continue to run on systemd, because it _works_.
SystemXVI will have systemd unit file compatibility. SystemXVI natively uses an INI-like file format itself.
SystemXVI uses SunRPC for communication. Writing a systemctl wrapper could be as trivial as a shell script.
But until then, the world will continue to run on systemd, because it _works_
The world doesn't run on systemd, and it isn't a "just works" thing in the slightest.
Redhat are betting their particular farm on systemd in RHEL7, and Debian (hence recent Ubuntu releases building to the 16.04 LTS) has adopted the suite.
Is the point you are making above based on the percentage of servers running earlier supported Linux implementations or on the existence of alternatives such as the BSDs?
It's basically their product, so...
> and Debian (hence recent Ubuntu releases building to the 16.04 LTS) has adopted the suite.
I think Ubuntu adopting systemd has less to do with Debian doing so and more to do with Gnome becoming increasingly difficult to package without systemd.
Does it?
When Debian switched to systemd my system stopped booting. When I managed to "fix" it, it worked superficially but displayed "Segmentation fault" at every boot [it still does that on another one of my machines, which in fairness never "broke".]. This in addition to boot-time fsck breaking and my bluetooth audio and keyboard setup no longer working. Based on this I am not inclined to think of Mr. Poettering as an "it just works" kinda guy. On a related note I have never successfully gotten pulse audio to perform its intended function of playing audio samples.
After ~15 years of mostly tracking Debian sid on my personal machine, I switched to FreeBSD on my laptop when seeing these issues. No major issues since.
I moved from Debian based distros to Arch a few years ago and found that my machines are a lot more stable. Because it you do the configuration yourself (rather than the configuration being in the package a la Debian), you are a lot more free to jettison dependencies of questionable quality. Though, I had a lot of trepidation when Arch switched to systemd, it has not yet broken my system in any way.
Still, there's nothing wrong with FreeBSD, so if it's working for you, might as will stay with it.
Every third update it will just start working and I'll think "Oh they fixed the bug". Then the next update breaks it again. I don't doubt that bluez must work well for some hardware, but for mine it is practically black magic to get it working.
My only point in fingering bluez is to say that bluetooth going down is not a surprising event on my machine and isn't related to systemd at all. I suspect the same is true of the OP's box. It was probably just a coincidence that bluetooth died at the same time that systemd was installed.
While the Linux code assumed the hardware was required to be up and ready in 2 minutes or less, the 2 minutes mentioned in the spec was just a suggested minimum wait time. Thus it would give up on devices that was still in the process of powering back on.
That not to say that bluez have been in great shape in recent years. But then it is also a complicated concept for *nix, as it straddles root and user. You have their whole pairing interface on the user side, and then all the device nodes (HID, Audio, etc) on the root side.