If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Maybe canonical noticed the bad pr they got from the mir debacle, and now they're trying to be like "look, we're not redesigning everything, we can still use components that are made by others"...

logind was accepted before Mir went public. What really goes on is Canonical adapting because they wont spend time on maintaning stuff. It appears Canonical can only be tamed by putting more stuff into systemds tree. Anyway systemds tree is populated by redhat, intel and linux foundation devs now. Wayland to systemd? It could happen..

I recently switch from OpenRC to systemd on my Gentoo system and the difference is incredible. I don't see why anyone would want to stick with upstart.

Why? Maybe you don't know the Canonical opinion about it: 100% control of the project.
Canonical just wait that you mature your work, when it performs good and it is ready, they fork it and continue the work in house.
Why talk with the project leader and his community when you can fork and do everything you want?
The dictator don't ask, the dictator command and conquer.
But if you haven't the people for continue that project in the right direction, after 1 or 2 years, the original project became better than the canonical fork and then they jump on the original and fork it again, or look to another project and fork it as well.
In both cases, no contribution will arrive upstream.
Contribution upstream? Never! This is the canonical's brand mark.

udev, logind, pam, etc.
It just feels like a big monolithic mess where components cant be interchanged.

I heard some talks before about something about GNOME depend on systemd?
Whats next, PulseAudio depend on it too?

Just one big monolithic stack.

Well, it is more like a number components working together consistently. It is much better than the mess that is system startup scripts written in bash.

Now we have a central place to handle authentication, session management, automatic multi-seat, screen locking, suspend, hibernate and shutdown/reboot with policy management. A few days ago I tried to shutdown the computer from a virtual terminal and systemd asked me my password. I am amazed that policy management works all the way from the terminal to the graphical interface properly. None of this could be done without a central mechanism.

And don't get me started writing initscripts using hundreds of lines stupid bash script compared to approximately ten lines in a systemd service file.

I am no way affiliated with systemd, but I am sure systemd is one of the best things that has happened to linux, for a very very long while.

udev, logind, pam, etc.
It just feels like a big monolithic mess where components cant be interchanged.

I heard some talks before about something about GNOME depend on systemd?
Whats next, PulseAudio depend on it too?

Just one big monolithic stack.

It is called CoreOS (sans Gnome stuff). And it is great, because it minimizes the maintaince burden. If YOU want to do something exotic just pull the sysd tree and cherry pick what you want. And if YOU dont like the crazy maintenance burden of extracting modules from the three, the YOU know WHY the systemd tree people DONT like to do extra loops of maintenance. So yeah YOU and out-standard-fuckers like Canonical can jump from a bridge, and please chain yourself to the crazy eudev forkster clowns as well.

A few days ago I tried to shutdown the computer from a virtual terminal and systemd asked me my password. I am amazed that policy management works all the way from the terminal to the graphical interface properly. None of this could be done without a central mechanism.

How peculiar, I could've sworn "sudo poweroff" has always asked me for my password, a decade before systemd...

logind was accepted before Mir went public. What really goes on is Canonical adapting because they wont spend time on maintaning stuff. It appears Canonical can only be tamed by putting more stuff into systemds tree. Anyway systemds tree is populated by redhat, intel and linux foundation devs now. Wayland to systemd? It could happen..

That's what pisses me off. Unilke Red Hat, SUSE and others, Canonical only maintains their own components with CLA. They use the community to get free labor, but they hardly ever contribute anything back upstream that is not Ubuntu specific (so the maintenance is handed over to the community).