am I missing something or is there a typo?
Hope there will be Lineage OS 17.1 added soon

thank you again for your GREAT work and maintaining PINN!
If you aren't successful with PINN, MultiBoot is compatible with all versions of RaspiOS as well as RetroPie and TwisterOS. MultiBoot supports specifying arbitrary partition sizes for each OS.
I did something similar.....and there were no problems....PLowran wrote: ↑Sat Nov 07, 2020 2:05 pmIf you aren't successful with PINN, MultiBoot is compatible with all versions of RaspiOS as well as RetroPie and TwisterOS. MultiBoot supports specifying arbitrary partition sizes for each OS.
Oh Really....
Everything I was reading said PINN was the way to go and that it has more & better options....
I was thinking this morning; What if I set up extra project spaces say....
Project Space 1: RetroPie
Project Space 2:Empty
Project Space 3: TwisterOS
Project Space 4:Empty
Project Space 5:Empty
Then Possibly use GParted, Delete Project Space 2: and Resize RetroPie to use the empty Space?
Then Delete Project Space 4 & 5, Resize Twister to use the empty Space?
Thoughts?
Yeah I just installed PINN right now and noticed it. Great app (OS? Installer? ¯\_(ツ)_/¯) btw! I never knew this many OSes were supported by the Raspberry Pi. But I have another question now. I selected TwisterOS and Arch, and I plan to install Gentoo later (maybe in summer holidays when I have free time), but when I press install, it says it will install the operating systems I selected, and 'All existing data on the USB drive will be deleted.'. Does that mean I won't be able to install more OSes later? I just don't want to be disappointed/shocked later.procount wrote: ↑Tue Nov 10, 2020 6:31 pmJust install PINN and boot it. It will present you with a catalogue of OSes (including Arch) that you can select from.
Please see the full instructions at https://github.com/procount/pinn/blob/m ... ME_PINN.md
Like NOOBS, PINN can install multiple OSes on one device (SD card, SSD HDD, whatever).
Well yes, they need to be big enough for the OSes that you will later install into them. You can't allocate a 512MB ProjectSpace and expect to fit a 5GB OS in it!
No, it is set from the beginning. PINN is not gparted!, but if you want to use gparted to adjust the partition sizes later, you could do, just don't change the partition numbers otherwise things may not boot anymore.
The Arch on PINN is the same as on the Arch website. It is a rolling release, so you always get the latest version. There are 3 versions of Arch depending on your Pi model, but PINN will pick the right one for you (unless you select showall). Highlight the Arch OS and click on the info button, it will take you to the webpage of that OS. It looks like Arch4 is still 32bit because it also talks there about Aarch64 (which I haven't converted).
Wow, thanks a lot! That's a pretty detailed explanation. I didn't want to go to Matt's webpage since I don't even know how much space I want to allocate for each partition, but since the blank space is shared out, I guess that's not really a problem, and since I can use GPartEd without changing the partition numbers, that makes everything easier too. tbh it doesn't really matter if it is 32 or 64-bit, as most of the RPi related stuff is 32-bit anyway, but I'd rather have 64-bit for future support. Welp it's too late now since I was in the middle of the install process when I saw this post, but I guess I could swap it out later by changing the partitions, or just allocating to one of 2 project spaces I allocated. I can use replace on an actual OS, right?procount wrote: ↑Tue Nov 10, 2020 8:59 pmI think a lot of this is answered in the documentation, but just so that are are clear with it:
Like NOOBS, PINN can install multiple OSes on one device (SD card, SSD HDD, whatever).
Each OS takes up a minimum amount of space depending on its size/features etc.
Any remaining space on your storage device is then shared out equally between all the OSes you have installed.
So after installation there is no more space to install another OS. Even if there was, PINN does not know how to add more OSes.
ProjectSpaces are a way to reserve space on your storage device for future OSes.
They're like OSes that have zero minimal storage requirements so they only get the amount of remaining storage space that is shared between all the OSes.
PINN can replace OSes with other OSes, so a ProjectSpace could be replaced by a different OS at a later date.
However, an OS can only be replaced by another that has the same partition requirements (number and size).
ProjectSpaces have a small fixed FAT partition and a flexible EXT4 partition for the rootfs, so they can only be used to reserve space for similar OSes (i.e. forget Android), but most OSes conform to this format.
Well yes, they need to be big enough for the OSes that you will later install into them. You can't allocate a 512MB ProjectSpace and expect to fit a 5GB OS in it!
No, it is set from the beginning. PINN is not gparted!, but if you want to use gparted to adjust the partition sizes later, you could do, just don't change the partition numbers otherwise things may not boot anymore.
As I said above, all remaining space is divided equally between the installed OSes. If you want more control over the allocation at the start, i.e. to allocate 30GB to Retropie for all your game roms, and only a few GB for Raspberry Pi OS, then go to Matt's webpage at pinn.mh.nz. Here you can select your Pi model, size of Storage card and which OSes you want to install. Then it allows you to set the specific amount of storage you want allocated to each OS using some nice sliders. Just adjust your recovery.cmdline according to the webpage instructions and your installation will be as you want.
The Arch on PINN is the same as on the Arch website. It is a rolling release, so you always get the latest version. There are 3 versions of Arch depending on your Pi model, but PINN will pick the right one for you (unless you select showall). Highlight the Arch OS and click on the info button, it will take you to the webpage of that OS. It looks like Arch4 is still 32bit because it also talks there about Aarch64 (which I haven't converted).
oh yeah I forgot to do that, thanks. Sorry if I'm annoying you with so many questions, but if there's anything I learnt from using Linux, it is to solve a problem from the very beginning before it escalates into something much MUCH worse.