3 ms·
I use separate debian nspawn containers for this kind of crap. It doesn't bother me to turn on multilib support in a rootfs I only boot in a container just to
by newnewpdro 7y ago
I use separate debian nspawn containers for this kind of crap.
It doesn't bother me to turn on multilib support in a rootfs I only boot in a container just to run steam client and its games. Though I do have to reboot into a kernel w/32-bit support first which can be annoying.
- yjftsjthsd-h 7y ago> Though I do have to reboot into a kernel w/32-bit support first which can be annoying. Isn't that in by default on pretty much everything? I'm not aware of any distro shipping an x86 kernel with 32-bit support disabled, anyways. Are you intentionally building your own kernels and removing 32-bit compatibility? Seems like an easier thing to fix than having to reboot every time.... (Unless I've misremembered and that is a default, in which case please correct me because that throws it the other way)
- newnewpdro 7y agoI build my own monolithic kernels, and only enable the features and drivers I use. My host is all 64-bit userland, it's just exceptions like Steam stuff that need 32-bit support (even the Steamworks/Steampipe developer side is annoying like this). So I boot into that kernel when doing those things, and keep those userspaces in separate containers which also get "booted" when needed.