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

Bug#727708: multiple init systems - formal resolution proposal - Don't like software, don't use it. Absolutely.



Sergey B Kirpichev <skirpichev@gmail.com> writes:

> Are X-people indeed sacrifice portability, or there is something
> different (e.g. these dependencies are optional)?

Speaking as the X server release manager, the systemd patches exist
solely to provide for interoperation with systemd or other similar
device management processes. None of them eliminate existing device
management infrastructure at all.

In effect, X takes the Debian position that patches which improve
interoperabilty with a specific init system should be integrated.

X is most definitely not going to ever require systemd. I think that any
package which requires a specific init system is broken and I'd work to
fix any that I depended on.

> Where is the list of problems for sysvinit we intend to solve?

For X, the problem is running X as a user other than root, which should
provide for increased system security as we'll be reducing the amount of
root code substantially. Using the systemd mechanisms for sending new
input devices to the X server solves one of the longstanding issues with
non-root X.

-- 
keith.packard@intel.com

Attachment: pgpgmVaSq4YR2.pgp
Description: PGP signature


Reply to: