Actively blocking fixes

Posted Nov 13, 2019 17:20 UTC (Wed) by khim (subscriber, #9252)
In reply to: Actively blocking fixes by smurf
Parent article: Debian reconsiders init-system diversity

The only way to get this to work in some stable kind of way (that I can see, anyway) would be a stub init that checks which real init should run, re-links the libsystemd0 symlink to point to either libsystemd0.whatever-version.so or libelogind.some-other-version.so, and execs the real init. Good luck doing that if [/usr]/lib should happen to be readonly.

I think I miss something really important here: you have to call mount once to bind-mount either libsystemd0.whatever-version.so or libelogind.some-other-version.so on top of libsystemdo.so... and that kinda implies root privileges... but PID1 always have them so... what's the problem?

Actively blocking fixes

Posted Nov 13, 2019 21:13 UTC (Wed) by NYKevin (subscriber, #129325) [Link]

That's probably easier/saner than mutating the filesystem on disk as the parent was proposing, but I imagine the likes of APT would be unhappy at finding a random mountpoint in the middle of their managed libfoo.so files. They could probably fix that, given enough political will, but the back-and-forth on that bug makes me rather skeptical of that outcome.