Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by Spivak on Sunday March 14, 2021 @10:26AM
(#26455709)
It’s not a hacked thing, it’s filesystem namespaces exactly as is done in Docker so that a container process doesn’t mess up its image.
It’s no more privilege than pid 1 had before because of .mount units.
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by Denvercoder9 on Sunday March 14, 2021 @01:13PM
(#26456905)
> forcing them to be used all the time
You know this doesn't do anything unless explicitly configured in the system and/or unit configuration?
Tying them to pid 1, and forcing them to be used all the time for some hacked up thing where /usr is different depending on which process is looking at it? Not so much.