procount
commented
3 years ago I'm not sure what you mean by "inflexible". If you want to convert another OS to PINN, there are instructions in the README - https://github.com/procount/pinn/blob/master/README_PINN.md#how-to-create-a-custom-os-version and a tutorial in the wiki - https://github.com/procount/pinn/wiki/How-to-Create-a-Multi-Boot-SD-card-out-of-2-existing-OSes-using-PINN that describe the general method of converting a common OS. But each OS is different and it can take a while to check if they work with USB root, USB boot, require specific labels, or need a custom partition_setup script etc etc. It is not a given that every OS can be converted to work with PINN. As it happens, I am using my own modified version of Sakaki's pinnify script to convert my OSes. When I get it finished I may even publish it, but it is not in a fit state at the moment. Her pinnify script on github was written for gentoo and requires some changes for other types of OS. I will add these OSes to my list of OSes to update or convert, but unfortunately this process takes time and disk space, neither of which I have much of at the moment.
I definitely prefer PINN over BerryBoot due to its stability(reliability), since it generates partition table based on the selection. However when it comes adding custom OSes, its very inflexible. I see several latest OSes(examples below) have been optimized for performance, and usability. However PINN does not support them OOTB.
I explored quite a lot on how to add a OS of your choice, however found not much, except sakari's project. However with that project, I wonder if I can download the xz image and provide local image file. I am not sure, if the Pinnify script (shell) would be able to successfully complete for above examples.
so if you could add support some of these popular OSes, it would be great thanks in advance :+1: :smiley: