On Mon, 5 Jun 2023, Simon McVittie wrote: >No init system at all, (C.), can only happen when starting with a >minbase debootstrap or equivalent (because a default debootstrap >includes the init metapackage due to its Priority: required). In >this scenario it *usually* doesn't really matter whether we >install systemd or systemd-tmpfiles-standalone. systemd is somewhat
This is not quite true; there is one really important use case: chroots. I have multiple chroots (sid, stretch, buster) on one of my bullseye systems which I use with schroot, but that could just as well be any other chroot, to run individual software in it. They are, as is proper, configured to not run any services (via policy-rc.d). >I also think that Policy shouldn't be recommending this interface without Therefore I belive that Policy ought to *not* recommend any solution that depends on starting dæmons or init scripts to create temporary files/directories that are necessary for programs to work. >- if we get a useful non-Linux port (admittedly this looks increasingly > unlikely) which cannot compile src:systemd, then their reimplementation hurd-amd64 is just shy of being uploaded; work on Debian GNU/Hurd is active and things seem to look good on that front. (The pools for hurd-amd64 have just been created a week or two ago.) bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg **************************************************** /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against Mit dem tarent-Newsletter nichts mehr verpassen: ╳ HTML eMail! Also, https://www.tarent.de/newsletter ╱ ╲ header encryption! ****************************************************
