Mozilla in recent releases is making it really hard for non-systemd distros to comply. Fake non-systemd distros using udev and elogind out of the latest systemd don’t seem to have a problem.…
This looks like a replacement for chroot itself. It would be better if i can spawn a systemd process inside chroot that take care of services. And i can’t understand why it wants to stick into PID 1 of host even when running in chroot.
At first sight, it looks like it can be used with chroots thanks to
systemd-nspawn(I haven’t tried it though)This looks like a replacement for chroot itself. It would be better if i can spawn a systemd process inside chroot that take care of services. And i can’t understand why it wants to stick into PID 1 of host even when running in chroot.