John Summerfield wrote:
More thoughts...
In syslinux configuration
linux rel=...
Use the value to chroot into the correct install environment
that might work if you can use the same kernel for both releases. Should be okay
in these particular cases, but may fail at some point such as when 2.6 comes out.
You might do it better by loading different kernel/initrd depending on the
selection from the boot menu.
First my setup. I created the i386 directory for RH 7.3 as usual. I
then added a 'rh72' directory in the i386 directory, which contains all
of my RH 7.2 files. I was hoping that John's suggestion about chrooting
would work.
I added an option in anaconda for rel=, and if it has 7.2 it does a
chroot `chroot rh72`. I tried this as an nfs install, but it obviously
didn't work, becuse the nfs install actually mounts the source
directory, and chrooting doesn't help. I am guessing that when I
finally get the discs, it won't work either. Are there any other
suggestions, or anyone that knows the inner code of anaconda that could
help? I was thinking that I could use a different loader, one that had
the rh72/RedHat/RPMS path instead of the standard RedHat/RPMS, but I'm
not sure how to use this other loader once I build it.
Finally, I tried to use implantisomd5 on the resulting iso image, which
turned out to be 2.8 GB. I get the error: Unable to open file. This
seems to be a problem with the 2.0 GB limit, because it worked fine when
it was 1.5 GB. Any ideas on how to fix this?
Thanks,
Forrest
--
