Re: Chainloadig from grub2 to isolinux

[Beeblebrox <zaphod@berentweb.com>]

>> yes,but a local repo takes care of that. (and that repo can be the contents of the cd)
>> extracting the kernel, initrd, cmdline and rootfs (I have done it with a gparted iso))

All that work is just so not worth it. I'd rather do something else with my time.

>> It is a monster, to extract each live.iso then copy the kernel and the initrd, then find out the correct parameters and loopmout it.

My thoughts exactly, tuxracer. It's why I made the suggestion (post 7 of this thread) for a wiki page showing grub.cfg entries using loopback for each individual distro. It would be incumbent upon the distro maintainers to test and submit the proper loopback menu entry, since they are the ones maintaining the distro (did someone say concrete proposals?)

>> There is no sane way to use isolinux cfg from iso simply because it's not designed to handle iso scenario, only real CD one.

I'm happy to have that cleared up...

>> If you use loopback.cfg as intended it will all work.
loopback.cfg contains the linux/initrd entries relevant to each distro's iso (or at least that's what the wiki page shows). That's exactly the problem - each iso has different settings for linux/initrd entries, and if you get them wrong, it really does not matter what file the entry was placed in.

Also as confirmed by ben, it's apparently not going to work on a number of Debian-based iso's. Usually the solution is to include casper in the CD to make this happen AFAIK.

May I suggest one more thing? I have "mail delivery" turned off for this list, and I must remember to check the mail-list web page in order to follow my threads. A solution would be to use nabble, where one can mark the threads to be followed. Posts to those threads will then be automatically delivered via email. There's about a half hour delay between a mail list and delivery to nabble, but it's better than a delay of several days.

Regards.