Idk if it changes anything but in that part of my comment the word “workspace” should’ve been replaced by “workstation”. I guess I chose a wrong word in autocorrect.
Nope, it doesn’t. But thanks for clarifying!
An immutable system is when everything (or almost everything) except for /home is read-only.
Interesting. Here’s the thing; I am unaware of any so-called ‘immutable distro’ that fits this definition/description/notion/idea/understanding of an immutable system. So…, where do we go from here?
Idk if my English was an issue there but it looks like you understood that part completely upside down.
In retrospect, I think you actually did an okay-job at explaining your thoughts. But, yes; I did indeed misunderstand. Thanks for clarifying!
Probably. Idk anything about ostree.
In Fedora Atomic, most of /usr is immutable. IIRC, this is even the only directory (combined with the sub-directories found within) that are immutable. However, the command rpm-ostree install <package> allows the user to install packages into /usr. However, this change doesn’t happen during runtime. Instead, a new image/deployment is created with the newly installed package that you can access after a (soft-)reboot (or with –apply-live if you like to live on the edge).
Based on this, does this still apply as “disabling immutability”?
What I meant is that if you want to manually edit a file anywhere except for /home (or do any manual changes to the system like installing a GTK theme), you have to run a command (I forgot which one) to disable immutability for the directory it’s in (or only for the file; I don’t remember).
This seems to be based on your own experience. If so, would you be so kind to inform me on which distro this was?
For new users it can be a problem because it may be hard for them to find a good tutorial that covers all the steps, especially at the start of the “immutability boom” if it’s ever going to happen.
Currently, apart from the documentation provided by uBlue and Guix, there’s definitely a lack of good resources for ‘immutable’ distros. That’s simply a fact. But, thankfully, this is not a problem by design; we just need people that are willing to put in the effort.
As I just said, more stability means that issues are more stable and hard to solve as well.
Sorry, I’m having a hard time understanding this. Could you perhaps provide an example of this from e.g. Debian? It can be any distro that’s regarded as *‘stable’**.
Unless I’m wrong, you seem to have missed the following. It would be awesome if you could touch upon these as well:
Furthermore, is it required that an immutable system should remain immutable at all times for it to be considered an immutable system; i.e. changes are not allowed besides ‘hacks’? Or is it perhaps possible for a system to be deemed immutable if it only possesses immutability during runtime?
Thanks in advance 😊!
WOW, I just noticed something. You’ve been using the term “immutable system” for quite some time. And, I’ve primarily been using the term ‘immutable’ distro.
GolfNovemberUniform