5 ms·
> A concept of system extension images is introduced. Such images may be used to extend the /usr/ and /opt/ directory hierarchies at runtime with additional fil
by hedora 6y ago
> A concept of system extension images is introduced. Such images may be used to extend the /usr/ and /opt/ directory hierarchies at runtime with additional files (even if the file system is read-only). When a system extension image is activated, its /usr/ and /opt/ hierarchies and os-release information are combined via overlayfs with the file system hierarchy of the host OS.
Oh, what fresh hell is this?
- chunkyks 6y agoTo be fair overlay fs is a good way to manage network boot / nfs root systems, live cds... All sorts of things where I want an underlying fs that clients can't mess with but they still need to think they can write to it
- hedora 6y agoOverlays are fine. I’ve used them for all sorts of stuff. 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.
- Spivak 6y agoIt’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.
- Denvercoder9 6y ago> 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?
- viraptor 6y agoIt's basically the ostree idea on a smaller scale. Did you ever want to install some proprietary software with access to system libraries/config, but without actually polluting the global namespace? It's this. Like running a docker service with host as your base layer. (Minus other namespaces) Honestly, it seems great and not very tricky for a system which already manages namespaces with private mounts.
- e12e 6y agoThere's a pretty big difference between "ghosting" /opt, /srv, /usr/local/ - and munging all/any of /usr?
- viraptor 6y agoNot sure what you mean either by ghosting or by munging to be honest...
- e12e 6y agoMunging - 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.
- viraptor 6y ago> 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.
- spijdar 6y agoJust 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.
- IgorPartola 6y agoJust because it comes from systemd doesn’t mean it’s a bad idea. OpenWRT and other embedded Linux systems use overlay file systems very effectively.
- crooked-v 6y agoThere's actually a directly analogous case in the gaming world, of all things: the app Mod Organizer 2 uses a runtime virtual file system There's actually a directly analogous case in the gaming world, of all things: the app Mod Organizer 2 uses a runtime-only virtual file system to layer together the files from different mod packages, making it easy to adjust for and dynamically disable/enable overlapping mod resource files (of which there can be a huge number in games like Skyrim), as well as redirecting output files from mods to a sane holding area instead of letting them pollute your game installs.
- 2ion 6y agoIt's a fine concept. Good for replacing stuff like appimage besides the packaging part? Mixing this with OS package management will require some consideration. So they are using overlayfs, which means that "upper" directories have visibility precedence on file name conflict. Which means that some auditing facility should be required that alerts if an upper sys image masks a lower one, or if an OS package some time later installs a file to the "lower" directory, perhaps the original rootfs, but a sysfs package still takes precedence…