Originally posted by Danielsan
View Post
Announcement
Collapse
No announcement yet.
systemd 248 RC1 Released With New "System Extension Images" Concept
Collapse
X
-
Originally posted by Shiba View Post
That's precisely what fstab is for.
How do you create new persistent mount points programmatically (= not by manually editing a file)? You can't.
How do you modify mount options programmatically (=not with grep/sed/awk)? You can't.
How do you ensure that something gets mounted if and only if the required resource (volume, network share etc.) is available and kicking? You can't.
How can users automatically mount an overlay or custom extension upon login in a private namespace? They can't.
How do you find *programmatically* (= not with "grep /var/log/...") which mounts have failed and why? You can't.
Etc...
Like most things in *nix, fstab is a vomitous kludge that has been hacked together with no foresight, no care for consistency or usability (other than by a script-happy sysadmin), no sane or predictable syntax and no unifying vision of how the OS should work as a whole. It's in urgent need of dying its ignominious death.
- Likes 2
Comment
-
Originally posted by pabloski View Post
Yeah, interesting, but I don't see these technologies coming to fruition. This is a new thing, but I bet we will never see a Linux distro capable of dynamically plug/unplug programs. People that have used Slax know what I mean.
You have a read-only "extension image". You double click on it and voilà , it merges with the root fs.
Also it is not clear how they will implement configuration of these "extension images" applications. The devs stated that /etc is off-limits. Will the configs be put in /usr/local/etc?? But I suppose this will require patching a bunch of programs that currently use /etc to store their config.
p.s. I am one of those people playing with overlayfs. I have settled on a "live" setup, with the rootfs mounted ro from a squashfs and the overlay in tmpfs. To maintain persistence for some programs, I use containers ( through systemd-nspawn ). So I have a base system that is ro and overlay in tmpfs and programs needing to "have memory" in containers on another volume ( a xfs one for various reasons ).
- Likes 2
Comment
-
Originally posted by Shiba View Post
That's precisely what fstab is for.
When you want to do runtime dynamic changes, fstab doesn't help at all
- Likes 2
Comment
-
Originally posted by RahulSundaram View Post
No, fstab is just a static list of mounts. I would start by reading
When you want to do runtime dynamic changes, fstab doesn't help at all
Originally posted by jacob View Post*programmatically*
Comment
-
Originally posted by skeevy420 View Post
Dear Penthouse,
Met the girl of my dreams last night. We clicked instantly and the next thing you know we had an overlay on the couch. She tried to mount me on dining room table but it crashed. No problem, we started right back up fscked all night long. She really knew how to ctrl the system's d.
Yours truly,
Linux Guy
- Likes 1
Comment
Comment