If you look through the anaconda source directory (at least for 7.2) there are about 100 places that it references something under the RedHat/ tree, with several of those being in .po files. It should be easy enough to sed -e 's,RedHat/,rh72/RedHat/,' through all the files, Remember to restore original permissions after doing that, I have had that one bite me. This is how I would do it . sed -e 's,Redhat/,rh72/RedHat/,g' on each file (probably done better in perl) . Rebuild new anaconda. . Install the new anaconda rpm. . Modify your directory structure/build script to reflect addition of rh72/. . Rebuild w/ buildinstall and related tools. . Repeate for 7.3 Now here is the intresting part. You should have cdboot.img's from both the 72 and 73 build install, combine them into one (how to fit it, I don't know) with a syslinux.cfg that has some entries like this: label rh72 kernel vmlinuz-72 append initrd=initrd-72.img devfs=nomount ramdisk_size=8192 vga=788 And and an equivilent entry for rh73 specifing the 73 kernel and initrd. The only problem I can forsee with this is trying to get both kernels and both initrd's into one cdboot.img. Good luck and let me know if it works. Joshua Aune On Tue, Jun 11, 2002 at 12:42:42PM -0700, Taylor, ForrestX wrote: > From: "Taylor, ForrestX" <forrestx.taylor@xxxxxxxxx> > User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020515 > To: anaconda-devel-list@xxxxxxxxxx > Subject: Re: Making a DVD Install CD > Date: Tue, 11 Jun 2002 12:42:42 -0700 > > 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 > > > > > -- > > > > > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/anaconda-devel-list > -- Josh
