@mirabilos@zvava@lanodan@hsza it’s an example. there’s no reason it has to be systemd. just saying that namespaces exist and we have tools to run things from a system root in a container-like env that are easier to use than manually setting up /proc /sys /dev and running chroot
@mirabilos@zvava@lanodan@hsza i don’t see how i can’t do that there. chroot changes the root dir of the process and has no influence on privileges otherwise
reminder that GNOME is not actually free software and also not part of the GNU project anymore, but rather a commercial product. the coordinating GNOME foundation is entirely corporate.
@tudbut@hsza sometimes things get faster and better though
e.g. wayland, niri and pipewire were all huge upgrades to my experience and i didn’t know i wanted them at the time. even the ancient eeepc 900 actually is more responsive now than it was 15 years ago
@zvava@lanodan@tudbut@hsza i am considering starting another RPM distro because i want to change direction in a way the opensuse project is not likely to agree with due to it being the basis for a commercial product
@tudbut@zvava@lanodan@hsza idk to me it’s like doing the laundry or something, so i upgrade stuff pretty frequently. tumbleweed never really broke anything for me. my desktop still has the same install from 2009 and i just kept migrating it to new hardware over time
@mirabilos@zvava@lanodan@hsza you can launch them from a privileged process that takes care of sanitizing the environment and setting up restrictions/sandboxing. e.g. systemd’s run0 does that
