News for hackers. Stuff that matters.
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by e12e on Saturday March 13, 2021 @08:51PM (#26452048)
Munging - messing with. Per the (somewhat abandoned)standard for filesystem layout /usr (except /usr/local) is the domainof the system/distribution. It's not very nice for a package to stomp on that. Although systemd already claim some authority over logs via journalctl of course.

Ghosting: by bind-mounting over the system fs -you might introduce a bug/condition that doesn't show up in a recovery boot scenario, or forensic analyzis of the filesystem/disk - you could introduce "ghost" files/artefacts.

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by viraptor on Saturday March 13, 2021 @09:05PM (#26452117)
> It's not very nice for a package to stomp on that.

Yes, sure. That doesn't stop hundreds of vendors with custom install scripts who will use /usr and /opt which is the current state of things. Systemd actually provides a workaround here which stops that package from changing those hierarchies globally, which... seems like something you'd want?

> you might introduce a bug/condition that doesn't show up in a recovery boot scenario

Why would you try to run anything but recovery tools in a recovery boot scenario?

> or forensic analyzis of the filesystem/disk

You can reproduce the same environment using the same overlay configuration - that setup is not hidden from you. It's not any more confusing in forensic than a docker service and we deal with them (including bind-mounts) just fine.

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by spijdar on Saturday March 13, 2021 @09:29PM (#26452242)
Just so we’re clear, unless I’m mistaken this overlay only affects the target software. It’s not allowing said extensions to trample the “root” file system. The altered fs only applies to a limited namespace.