Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
The updater downloads an updated copy of your root system and saves it next to the one you're running.
When you reboot the next time, the bootloader boots from that new system image.
Userspace applications are installed as flatpaks and sit in a writeable directory.
And "the updater" is what? A program running as [not root]? How does it have write access if nothing does?
It's the package manager. And it doesn't have write access to your installed root either.
It doesn't change anything on your installed file system at all, it installs a new system next to it.
So it installs a whole new filesystem? Interesting. That feels like it sets limitations on how well you can take advantage of the full space of your hard drive.
And this action can only be performed by the package manager running under some magical God user that sits above root? Or some other mechanism?
It utilizes the copy-on-write functionality of the BTRFS file system.
So it doesn't need double the disk space, it only actually writes the differences between your installed system and the new one.
And it runs normally with sudo, not some special god user.
You could do it manually, too.
So root still has write access to the system then, gotcha. Then it's not really immutable per se, the package manager just has a different way of writing to the filesystem that simulates immutability, I guess?
No, not while the system is running. The base-layer of the OS is fully read-only.
An update doesn't write to the existing system, it creates a new one that will be switched to on next reboot. So the current system is not actually changed, hence the term immutability. This has two benefits:
I get the feeling you're deliberately trying not to understand.
Maybe read up on how it works yourself, since I don't seem to get through to you.
The hell? I'm trying to confirm whether I understood correctly or not. You are definitely mistaken.
Never mind, I'll find someone more polite.