Hi,
Great job !!! .
you said:
"when a image boot
a) boot with vmlinux that is on DREAM-BOOT , with /lib/modules/ that is on image in OMB or ROOT
b) this vmlinux with modules MUST BE from the same compile-build image base from pli or openatv
c) not possible ,for example, to boot if vmlinux on DREAM-BOOT is pli and modules on multiboot image is from openatv or the opposite
d) possible to boot image base pli, with vmlinux - modules from openatv or the opposite"
That is clear.
If I understood correcly the booting process, vmlinux is first booted from "Vfat" partition an then the process jump to sdx2 "ext3" partition when you have an external flash image which must have the OMB plugin installed. The OMB task will be responsible of booting the image seleted from the omb menu using the proper vmlinux and modules. If this is the case?
In principle I need to change the vmilux in the DREAM-BOOT only if I decide to change the image in the "external flash" if needed . Is this the case ?
I didn't like omd in flash image because the booting process is much longer and because the writing of vmlinuz on the flash not always work correctly. I didn't like other Multiboot pluging like Italyboot (which is what I was using mostly) because of some incopatibility with newer image that creates issue with samba or OpenVpn.
So I 'm actually using an "homemade" usb-boot in which each image in store in a partition of the usb pen. I use a script to boot a different image. Basically this script copies the Boot content of the selectet image to the "vfat" partition. The "autoexec_dm800se.bat" is of course modifiet to point to the partition of the select image. In This way I've solved all compatibility issue,