Timeline for Ubuntu 16.04.1: Why are some programs started by both systemd AND initV systems?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2017 at 6:19 | vote | accept | the_velour_fog | ||
| Apr 3, 2017 at 11:28 | answer | added | Stephen Kitt | timeline score: 2 | |
| Apr 3, 2017 at 6:30 | comment | added | the_velour_fog | @jordanm I can understand that alternate init systems need to be supported because many programs in the apt package ecosystem and in the linux/unix ecosystem in general would expect the init scripts to be available during a session, but during boot, shouldnt only one mechanism be necessary to start a daemon? | |
| Apr 3, 2017 at 6:21 | comment | added | jordanm | Because Ubuntu inherits this stuff from Debian where alternate init systems are supported. | |
| Apr 3, 2017 at 5:45 | history | edited | the_velour_fog | CC BY-SA 3.0 |
added 2 characters in body
|
| Apr 3, 2017 at 1:20 | history | asked | the_velour_fog | CC BY-SA 3.0 |