1787
Comment: New proposal: multiple initsystems
|
1797
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
6. [[debate/initsystem/multiple|multiple]]: commit to supporting two or more specific initsystems, such that the default less important, and at least one of them is available to every arch | 6. [[debate/initsystem/multiple|multiple]]: commit to supporting two or more specific initsystems, such that choosing a default is less important, and at least one of them is available to every arch |
Debate Init System To Use
Current Options
(These options are not in any particular order)
sysvinit (status quo)
- One system on Linux, something else on non-linux
multiple: commit to supporting two or more specific initsystems, such that choosing a default is less important, and at least one of them is available to every arch
Summary Table
Option / Question |
?openrc |
|||
Hurd support/planned/welcomed |
Y |
N/N/Y |
N/N/Y |
N/Y/Y |
kFreeBSD support/planned/welcomed |
Y |
N/N/Y |
N/N/Y |
N/Y/Y |
sysvinit files compatibility |
Y |
Y |
Partial |
? |
Service file format |
SysV |
unit (ini-like) |
job (specific) |
? |
Socket activation support |
N |
Y |
Partial |
N |
D-Bus activation support |
N |
Y |
? |
N |
logind interface |
N |
Y |
Ubuntu patches ? |
? |
Reliable service/session shutdown |
N |
Y |
N |
N |
Open Questions
(These questions are not in any particular order)
- Transition plan
- Support for Hurd/kFreeBSD
- Support for init.d scripts
- Support for other systems
- ????