On Tue, 25 Mar 2008, Adam Hawks wrote:
> I changed the boot CD to have a SLES 9 and a SLES 10 kernel and initrd.
> And since root is in different locations on SLES 9 vs SLES 10 then
> linuxrc loads the corresponding install system.
> YaST is correctly starting with the install system for the correct SLES
> and reads the profiles without failing.
> I STILL have the problem that my CD doesn't request the SLES 9 or SLES
> 10's CD #1 when initializing the software catalogs.
> With SLES 8 you had the SLES 8 CD #1 and the United Linux CD #1 and you
> could boot from either one to install depending on whether you wanted SLES
> or United Linux.
> My situation is like the SLES 8 model where I have my RPM's that need to
> be installed on top of SLES 9, SLES 10 during the install.
> The only difference is I need to support both SLES 9 and SLES 10 as the
> base product.
> So I guess my basic problem is two fold.
> 1) How do you correctly layout a CD distribution with multiple products
> (mine on top of SLES 9 and mine on top of SLES 10)?
> 2) How do you create a boot CD that is an add-on to the existing SLES CD's
> without remastering CD #1 of SLES?
Hm, I can't comment on the required layout for add-on CDs but if you
remove the 'root' images from your CD, linuxrc assumes you have a special
boot CD and will ask for CD1. Maybe that helps.
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org