August 8th, Debian began supporting¹ choice among several init systems. August 21st, Debian changed² default init. To me, flexibility is an important feature of Debian. I am excited that Debian extends its flexibility to cover several init systems. Others agree, apparently³: Among those testing our system while this new flexibility is in place, ~20% use a non-default init system. For fresh installs, picking a non-default init requires a workaround: First install default init system, then replace with your own choice. Remember to also check for and purge any cruft pulled in by that detour. October 17th a fix was proposed at <https://bugs.debian.org/668001#20>. @Testers of Debian: Please test debootstrap with that patch applied and report your experiences, good and bad, to <668001@bugs.debian.org>. @Debian-installer team: Please reconsider applying that patch. If not targeted Jessie then in another suite: Any degree of adoption eases ability to test, which in turn eases ability to adopt further. Kind regards, - Jonas ¹ Package "sysvinit" stopped being flagged as essential, causing package managers to no longer treat alternative choices as breach of Policy. That changes entered unstable 2014-08-06 and testing 2014-08-12. ² Package "init" switched to favor "systemd-sysv" over "sysvinit-core". That changes entered unstable 2014-08-21 and testing 2014-08-26. ³ According to <https://qa.debian.org/popcon-graph.php?packages=sysvinit-core+systemd-sysv&from_date=2014-07-24&hlght_date=2014-08-26> -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: signature