[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Proposal: switch init system to systemd or upstart

Am Freitag, 25. Oktober 2013, 14:29:54 schrieb Marco d'Itri:
> It is more and more obvious that modern software needs an event-based
> init system.
> Pros:
> - more features
> - stable support for advanced boot/SAN environments
> - being more similar to one of the other relevant distributions (RHEL or
>   Ubuntu)
> - things like gnome become easier to package
> Cons:
> - some work to do (how much depends on the choice and on the details.
>   but keeping sysvinit on life support is not free either)
> Since the init system strongly shapes many other packages, there has to
> be only one and no other supported options.

I am just packaging a few packaging that I get sponsored from time to time, 
but for me for systemd to be acceptable a thing like

upower: authentification is required for hibernating while other users are 
logged in

systemd: authentification is required for hibernating while other users are 
logged in

Bug#727645: polkit-kde-1: requires root password for hibernate, wrongly 
reports other users are logged on

have to be solved *first*.

And as a user / tester of systemd I don´t even care as to where the fix has to 
be made or whether systemd or something else is made responsible for the 

But so far I have the impression my #717… bug reports back in June has been 
met with quite some amount of ignorance. Now someone else also reported it. 
And since it happens for any KDE + systemd setup with kdirmngr involved, I 
expect more "me toos".

I generally do like systemd, but thats what I feel uneasy about.

If systemd is decided to become default init, its important to treat bugs like 
this seriously.

I am back with insserv for months due to this issue.

Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Reply to: