Vu+ Multiboot - so to summarise many of the above points.
1. its not a Neutrino system, so doesn,t change the standard way of building Vu images used by OpenPli or the OE-A images
2. All OE-A images use the same build environment for their images, the same Vu+ meta and the same ofgwrite
3. In terms of E2 and Vu4K boxes, the OpenViX/OpenBH image will quite happily run as a single partition image
4. IF the user wants he can initiate a Multiboot system using the eMMC that can host quite happily any image (flashed using the OE-A ofgwrite) that uses as a basis the multiboot code written by Littlesat some moons ago.
5. Also if the user wants he can flash (using the same OE-A ofgwrite) an image to a USB hdd, used for holding the images.
This latter implementation does require a small change to multiboot.py to convert the UUID in the STARTUP files, to the actual mount used in the image.
The UUID was used to handle multiple HDD devices and switching of mounts, so that we always identify the correct USB image drive.
Overall, this implementation is very simple and straightforward compared to a certain HiSilicon box that uses an external device for images.
Like Rantanplan, I can never understand why users want to load up many images (often 10+), but for my uses multiboot is a great tool & test bed.
Gigablue Quad 4K & UE 4K, Vu+Uno4KSE, DM900
.........FBC Tuners:
------------------> GT-SAT unicable lnb to 1.5M dish(28.2E)
------------------> Gigablue unicable lnb to 80 cm dish(19.2E)
Octagon sf8008, AX HD61, Edision Osmio 4K+, Zgemma H9Combo using Legacy ports on multiswitches
Zgemma H9twin & Zgemma H9 C/S mode into Giga4K