On Tue, 18 Feb 2014 22:07:12 +0400, Andrew Savchenko wrote: > > Then write. Just be aware that to write a systemd profile, you need to > > use systemd. > > Or to create a non-systemd profile :)
We already have many of those, because systemd is not the default. Part of making it the default, if that decision is ever taken, would be to modify the current profiles to support systemd, at which point the old versions would become the non-systemd profiles. Yes, it does take systemd users/devs to create a systemd profile, but they are the one that will want to use it anyway. The rest already have what they want. This is the way things have moved with the GNOME and KDE profiles, expect others to follow suit. I'm still uncomfortable with the pervasiveness of systemd, although Canek does put forward persuasive arguments, through a mixture of expertise and remaining calm. So GNOME want to use logind, which may well be superior to ConsoleKit, but why should that require a change of init system? A login daemon should be started by the init system, not be an integral part of it. What happens when logind no longer fulfils developers needs, as is the case with ConsoleKit now, how can it be replaced with an improved service when it is so closely tied to the init system. -- Neil Bothwick Windows '96 artificial intelligence: Unable to FORMAT A: Having a go at C:
signature.asc
Description: PGP signature
