Why do you need to burn a new img each time and so regularly? Are you creating your own custom Retropie images, or using nightly builds?I can’t have pinn on the ssd alone because i’m going to burn a .img image to the ssd, and replace it in the future. And burning a .img wipes the ssd each time.
PINN can replace your OS in-situ (it just needs converting to tar format), or you can loop mount your img file and copy the partition contents yourself.
PINN cannot boot into a boot partition on another drive (e.g. Retropie) just like Autoboot since it is a firmware limitation. It can only work if Retropie's boot partition is on the same partition as PINN, although it's root partition could be on the SSD. This means if you write a new image to the SSD, the boot partition on there will be ignored unless it is copied to the SD card as well. (Although you could still use boot_order to switch).Could I install pinn on the sdcard, raspbian on the sdcard, retropie on the ssd, and then wipe the ssd and burn a new image to it, would pinn still see and select the ssd os after I replaced it?
It's possible, but it's not something I would recommend. Eeproms are not designed to be written regularly.I’m looking into changing boot_order instead, it seems simple enough in principle;
does it mean invoking that command to edit the eeoprom file directly, and not a config file somewhere?
Is this what raspi-config does when selecting it from the menu? a way to achieve this programmatically would solve it for me.
Statistics: Posted by procount — Wed Jan 10, 2024 12:35 am
