Comment on Manjaro Immutable out now for community testingComments−revscat2yWhat is this.−nextos2ySkim through this survey: https://ceur-ws.org/Vol-3386/paper9.pdfBasically, most of the system is read-only and updates/rollbacks are atomic.This approach means classical distributions can enjoy some of the advantages of NixOS.−christophilus2yManjaro is an Arch Linux-based distro. It has an experimental immutable implementation which is now out for community testing.−akkartik2y"immutable" is the part I'm not sure I understand. Does it mean you can roll back upgrades to any package, like in Nix?−andrewstuart2yImmutable means it does not change.Presumably this means that the operating system is effectively read only.This is good for applications where you want things to be very stable.−akkartik2ySay we find a bug in the operating system. What is the procedure for fixing the bug?−djbusby2yDeploy an updated, but immutable image.Like, Partition1 has v1 and you boot, read only. Then the upgrade image goes in Partition2 and boots readonly.You can still upgrade but every boot of the image is from the same fixed state. And you don't upgrade in-place.−c0balt2yThey do "atomic" updates for immutable distributions, effectively treating an "apt update" always as an update for all components. There's some systems for this that usually require a reboot afterward to load the new system version.−ukuina2yIs this like a Live CD?
Comments
What is this.
Skim through this survey: https://ceur-ws.org/Vol-3386/paper9.pdf
Basically, most of the system is read-only and updates/rollbacks are atomic.
This approach means classical distributions can enjoy some of the advantages of NixOS.
Manjaro is an Arch Linux-based distro. It has an experimental immutable implementation which is now out for community testing.
"immutable" is the part I'm not sure I understand. Does it mean you can roll back upgrades to any package, like in Nix?
Immutable means it does not change.
Presumably this means that the operating system is effectively read only.
This is good for applications where you want things to be very stable.
Say we find a bug in the operating system. What is the procedure for fixing the bug?
Deploy an updated, but immutable image.
Like, Partition1 has v1 and you boot, read only. Then the upgrade image goes in Partition2 and boots readonly.
You can still upgrade but every boot of the image is from the same fixed state. And you don't upgrade in-place.
They do "atomic" updates for immutable distributions, effectively treating an "apt update" always as an update for all components. There's some systems for this that usually require a reboot afterward to load the new system version.
Is this like a Live CD?