Why over-complicated? I’m genuinely curious, as I think it sounds pretty cool that you can install apps from different package managers in containers, but export them to use them in your main environment.
I briefly looked documentation, all the tools they provide, etc. Why we need supporting both rpm, deb and own format too? Why Debian? A/B is better than btrfs or symlinks? Maybe I should read documentation more, but why? It sounds really complicated with too many whys (and whay more why’s even compare to NixOS, being hardcore, but plain simple why).
What are updates if it is Debian Sid? Updates to software will replace A and B? Or do you install everything to A and B replaces A only with next OS update?
That is what I also read on main page. It is not clear will Firefox package require reboot to be applied.
BUT!
Than you read this in documentation:
abroot allows you to install kernel modules, drivers and other essential packages without compromising the filesystem’s immutability.
When a command gets executed in abroot, a transaction gets started in the transactional shell in the second root partition. If the transaction succeeds, the changes are applied using an overlay and synced with the current root on reboot. If the transaction fails, no changes are applied (due to a property known as atomicity). abroot also allows for on-demand transactions using the abroot shell command.
So Firefox is probably not a thing to switch A and B? But what happens if some package is successfully applied, B synced with A, after reboot it did not worked and you can not boot back.
Also both partitions will be minimum 20gb, that’s 40 allready. If you install 5gb package, it is successful, it will install 5gb package again… That’s double time! And No garantee the system will boot. Or it won’t be synced until it boots… Yet it could hang in 3 minuted after ram leak, and both A and B are synced, you will have 3 minutes to fix things after boot. Like uninstall that package. Instead of simple rollback.
Looks bad in comparison with Silverblue where I can pin many previous version. Thanks to OSTree, you can downgrade to any point in the history or even switch back to an older release.
deleted by creator
Why over-complicated? I’m genuinely curious, as I think it sounds pretty cool that you can install apps from different package managers in containers, but export them to use them in your main environment.
I briefly looked documentation, all the tools they provide, etc. Why we need supporting both rpm, deb and own format too? Why Debian? A/B is better than btrfs or symlinks? Maybe I should read documentation more, but why? It sounds really complicated with too many whys (and whay more why’s even compare to NixOS, being hardcore, but plain simple why).
deleted by creator
What are updates if it is Debian Sid? Updates to software will replace A and B? Or do you install everything to A and B replaces A only with next OS update?
deleted by creator
That is what I also read on main page. It is not clear will Firefox package require reboot to be applied.
BUT!
Than you read this in documentation:
So Firefox is probably not a thing to switch A and B? But what happens if some package is successfully applied, B synced with A, after reboot it did not worked and you can not boot back.
Also both partitions will be minimum 20gb, that’s 40 allready. If you install 5gb package, it is successful, it will install 5gb package again… That’s double time! And No garantee the system will boot. Or it won’t be synced until it boots… Yet it could hang in 3 minuted after ram leak, and both A and B are synced, you will have 3 minutes to fix things after boot. Like uninstall that package. Instead of simple rollback.
IDK I do not get it.
deleted by creator
deleted by creator
Looks bad in comparison with Silverblue where I can pin many previous version. Thanks to OSTree, you can downgrade to any point in the history or even switch back to an older release.
deleted by creator