How do *I* «install» and remove different versions of *my* ?

⚠ Warning: The following pictures may cause seizures in Linux traditionalists. I advise viewer discretion.

- No installer is required, and no installer setup is needed.
- The distribution lives as a single file.
- The root is *immutable*; however, selected paths can be writable.
- No need to create multiple partitions for new installations; I can have multiple versions (and their backups) in the same partition.

- System images are copied, not extracted; installing or uninstalling means copying or deleting a *single file* (literally), just like managing end-user software using AppImages.
- System installation takes seconds or minutes, depending if it's a local file, a file in a local network, or a file on a web server.

Let me summarize if you don't know how traditional installers work, and you will understand why I put «install» in quotes.

Any Linux distribution installer, past and present, first creates as many partitions as you've selected. Then, the installer extracts the SquashFS file inside the ISO image and dumps its content to the selected block device, for example, using rsync.

Then, the installer does a chroot to configure the «installed» system; for example, this is how the installer adds your user(s), adds and generates bootloader entries, and installs or removes packages (i.e., the installer package and its dependencies) etcetera.

Then umounts the chroot, and this is where you reboot to your freshly installed distribution.

That said, well, znx does not do that. It does create partitions (two, ZNX_BOOT, which is the EFI, and ZNX_DATA), then *copies* the ISO image to the appropriate path (/isodevice/STORE, which is a directory in ZNX_DATA), and that's it. The computer will boot the bootloader in the EFI (i.e., GRUB), then I can select which image to boot.


No, sorry...

Your post was the first time in over 30 Years that made a tiny, tiny light of remmembrance light up in my mind.

Deep, deep in my mind....

@uri_herrera GNU/Linux ecosystem has in use: 3 init systems, 10 DEs, 2 display servers, 4 file systems, 3 packaging systems, 3 portable packaging formats, endless combinations of distros. Why do you think someone who is looking at a work that is done within such an ecosystem, would be hurt?

Sign in to participate in the conversation

Everyone is welcome as long as you follow our code of conduct! Thank you. is maintained by Sujitech, LLC.