I have to say AEON has been teaching container and distrobox so much in 3 days or so and I am really started to understand the idea and system so much more how things are meant to be done. Thank you all for excellent work and forum support this is the one I am going to stay now on
AEON speed run full wipe from bios install aeon and all apps and settings with containers as it was before and the BTRFS extend took only 30 minutes total
some more details after 2 cups of coffee and getting wake up as i read my earlier answer it was terrible sorry about that…
How did you backup and restore containers?
my experiment was coming after messing around on containers and getting DaVinci working and running there and it needs FUSE to run appimages and FUSE was automounted and caused so much issues after delete container so i choosed to wipe full system no backups to use and see how long it takes from zero to fully setup working daily setup
How was system setup (layering core apps, etc.) done after installation?
base image installation took less than 1 minute and then after restart getting flatpaks from first start customize option it took for me about 10-15 minutes to download flatpaks that was around 80% of those already i use and need after that i just downloaded rest flatpaks when downloading flatpaks i used terminal to setup my second NVME to expand current BTRFS and changed host name, enable Nvidia repo and get drivers installed.
after restart just setup distrobox main container and install rest apps you need and export those to host.
main installation is minimal, but after first boot you can choose many apps already as first boot setup and setup your profile/account etc
If you use flatpaks, snaps, or AppImages how was it backup and restored?
pika backup is good tool to backup your HOME basically you dont need full back for system level since all apps basically is installed user level, flatpaks and then containers
do not use fuse it wont work and after i got it working it caused way too much issues so use only flatpaks and containers to get apps you cant get as flatpak
during post installation process how many times you had to go to transactional shell update mode. Think of changing host name, installing codecs, etc
transactional shell updates basically NONE total 3 times transcational-update. Enable nvdia repo for aeon and installing nvidia drivers and last time manually assign MOK keys since install script fails to get ROOT PW HASH ( this is the way need to do, but currently there is some bug where it dosent enable automatically nvidia so need to do temp fix editing conf.file and creating initrd for boot). codecs etc are there already
did you go rogue by installing it next to an existing OS partition?
no full wipe from bios clearing everyhting TPM reset, custom keys everything wiped as it is only OS i use as daily for work and personal
about the upgrades, in what way you can schedule it on a less frequent basis e.g. every 2 weeks and during the time that you’re not using the system
upgrades are automatic and working as background and applied when you shutdown or restart. Flatpak updates you run when it popups there is updates and thsoe ones are only ones you will see even
were there apps that you needed and not available as flatpaks, so you had to fallback to transactional shell updates
no main point going for this is keep base and core as clean and default as it is meant only nvidia drivers are added there since it is needed to run hybrid/optimus systems all others i look flatpaks and if not flatpaks i have main container from distrobox where i install packages or apps i need and dont have flatpaks
main experience is this is SICK and AWSOME no need to go anywhere else and by this i have been using Fedora 2 years straight one machine had workstation and laptop/daily i used silverblue and this wins silverblue on my opinion. It made me switch all my systems to openSUSE
Zero times is the correct answer. transactional-update shell is not for system management. If you’re diving into shell to do things, unless you’re debugging or testing things, you’re doing it wrong, and can potentially be putting your system out of support.
The update frequency can be adjust at anytime locally, by adjusting transactional-update.timer
Again, this is not a supported operation, do not use transactional-update shell for system management or package installation. The Aeon developers have been quite clear, that if you do so, and break things, and then file bugs or ask for support, you will no longer be in a supported configuration, and any bugs will be closed WONTFIX.