Systemd and ConsoleKit
Posted May 6, 2011 12:57 UTC (Fri) by anselm
In reply to: Systemd and ConsoleKit
Parent article: Systemd and ConsoleKit
I would say that this is one of the reasons that free (as in free beer, but possibly by extension as in free speech) software will have a hard time reaching a high number of private desktops. Many people can't afford to depend on software for which the maintainers don't have some sort of obligation to them
When people decide to run Linux on their private desktop, they won't usually make that contingent on the fact that their Linux distributions run specific technology such as System V init and ConsoleKit. They're in it for the complete picture. When they install a distribution such as Debian or Fedora, they put their trust in the maintainers of that distribution to keep their systems running, not to maintain whatever selection of software packages they had originally installed, for eternity.
I don't think anyone who has made the move to Linux will consider going back to whatever they ran before simply because their Linux distribution is moving to a different type of user session switcher. If OpenOffice.org/LibreOffice were suddenly to disappear from view, that might be a problem for many users but for most of the basic infrastructure this is simply not the case because people don't tend to notice the individual software packages involved.
It is safe to say that most people will not care in the least whether their systems run System V init/ConsoleKit or systemd, as long as their systems run reliably and as long as, if they have started out with a setup based on System V init/ConsoleKit, the eventual transition to systemd happens in a way that does not lead to regressions or other noticeable problems.
to post comments)