Earlier this month, Debian development team to create a poll to decide whether or not to support non-systemd initialize the system. Voting has now ended, the voting results are published.
The vote was a total of eight options include:
- Continue to focus on systemd
- Select systemd But while exploring alternatives
- Support for multiple initialization system is very important
- Support for non systemd initialize the system, but to avoid affecting progress
- Support portability, to avoid affecting progress
- Support for multiple initialization of the system is necessary
- Portability and support multiple system initialization
- The need for further discussion
According to the results released by Debian , and the winner of the poll options are:
" Systemd But WE Support Exploring Alternatives ."
(Choice but to explore alternative systemd)
For this option, the proposal initiated by developers but also about his thoughts:
Debian Project recognizes systemd service unit is used to describe how to start the daemon / service preferred configuration. However, Debian is still an environment, developers and users in which you can explore and develop alternative initialization (init) systemd alternative systems and functions.
Those who are interested in exploring such alternatives need to provide the necessary resources to develop and package the job done. When you run systemd rely on some software interfaces, such as elogind help explore alternative technologies like still important for Debian. More importantly, the team must support the development of Debian developers of such technologies, there is an overlap between the rest of these technologies and the Debian project, for example, check the patch in time and participate in discussions.
Packages should include service unit or startup scripts to start daemons and services. Packages can be at the discretion of systemd package maintainers to use any tool, as long as it is consistent with other policy requirements, and is generally recommended that the package should not be relied on unsupported experimental or other software packages (in Debian) function. Packages may include support for other than systemd init system, and may include any alternatives systemd specific interface it uses. Maintenance personnel use their routine procedure to determine the patch to be introduced.
Debian is committed to using derivatives to make a different choice of init system. And we all interact with downstream as associated maintenance personnel will work with the downstream, to find out what changes added to Debian fit in, what changes should be fully preserved in the derived tool.