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..
Originally Posted by dee.
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.
It really sucks that everything is dependent on systemd now.
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.
Originally Posted by uid313
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.
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.
Originally Posted by uid313
Last edited by funkSTAR; 03-07-2013 at 06:54 AM.
So you have not used upstart and yet have an outspoken opinion about it?
Originally Posted by nukem
How peculiar, I could've sworn "sudo poweroff" has always asked me for my password, a decade before systemd...
Originally Posted by aavci
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).
Originally Posted by funkSTAR
I hope they admit defeat and adopt systemd someday.
Last edited by newwen; 03-07-2013 at 06:57 AM.
The point is, you dont have to write sudo. It will check the policy and do "the right thing", shutting down right away, asking for a password or simply give an error.
Originally Posted by curaga
Not a big thing, it just shows the integration level. But I guess you don't like policykit either, then you are simply not in the intended audience.
Also, I didn't say that I was amazed because it asked for a password, I was amazed at the "integration level of the policy management". sudo has nothing to do with policy management.
Last edited by aavci; 03-07-2013 at 07:31 AM.