>> In the past I've used the `grub-imageboot` package for that.
> Near as I can tell, somewhere along the line the kernel and initrd are
> extracted from the (CD|DVD|diskette) image.
IIUC `grub-imageboot`s boot entries boot the ISOs by running the
`memdisk` program, passing it the ISO. I don't really know how
`memdisk` works internally, but I don't think it knows about initrd and
kernels because it also works to boot non-Linux images.
> My software doesn't even require that. Grub will reach into an ISO for
> them at boot time if you ask it politely.
> On brief investigation, this seems to require a lot of undocumented
> manual work to get things set up; I've automated a lot of that.
Ah, so it doesn't require something like `memdisk`, good.
>> AFAICT it requires you put the `.iso` files in `/boot/images/` which
>> is impractical for large ISOs, so maybe you could try and contribute
>> your code to that package.
> Not required; one can change that in /etc/default/grub-imageboot.
> One would have to in order to get the images onto their own isolated
> partition, one of the things I've done.
AFAICT it can be moved to another partition, indeed, but all the images
still have to be stored in the same partition (on a file system which
Grub can read). IIUC in your case, they can each use their
own partitions.
Stefan
