ady wrote:
An alternative method to memdisk, would be to expand each ISO image and use ISOLINUX/SYSLINUX directly. I won't get into the technical details. You might be interested in using auxiliary tools such as YUMI, SARDUCD, LILI, or some of their alternatives under Linux.
I'm interested in exactly that. Reading through the documentation, I see how memdisk works and what its limitations are. However, many images of interest are themselves built using ISOLINUX, and it should be easy to merge that in to the single USB thumbdrive.
The one I just looked at, though, uses an old ISOLINUX 3.x from 2011 and the files and directories don't match the current documentation.
I think the help should be expanded to show how to add images by expanding the ISO file and adding a line somewhere. That should be a simple recipe... Although the boot process can be just about anything, it seems that in all cases the MBR 512-byte c16 file does nothing more than load something else and run that. So, knowing which file to nominate on the CONFIG/LABEL/whatever line should do it. Except the loaded thing needs to know what its logical root is, and allow that: maybe ISOLINUX hides that by updating the BIOS first?
In practice, one of several common systems would be used, and the tutorial would aid in identifying which you have and what lines to add.
I'd be happy to help by editing the wiki page and contributing a summary of what worked for me.