The Wanderer <wande...@fastmail.fm> writes: > Unless my understanding of the architecture of systemd-the-init-system > is entirely incorrect, running these .service'es is handled by > /bin/systemd. If having these programs run at boot time is considered > essential to full functionality of these facilities - and I'd be > surprised if it wasn't - then something is going to have to be done to > permit that to happen under other init systems.
So create a package with init scripts (or runit scripts, or OpenRC scripts) that run those binaries, and make that package depend on systemd (*not* systemd-sysv). This seems fairly simple to me. Am I missing something (beyond the fact that this is problematic on the Hurd and kFreeBSD)? > If the maintainers of systemd-the-package would be willing to not only > split out these binaries into standalone package(s), but accept such > init scripts for inclusion in those packages, Why would that be necessary? -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
