Re: [opensuse-autoinstall] Custom autoInstall boot CD for multiple distributions (SLES 9 & SLES10)
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. Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
If I remove the root image from my boot CD linuxrc does ask for CD #1 of
SLES, but it then fails reading my profile's which are on my CD.
I got the SLES 9 kernel, initrd, root and my profiles to correctly boot
and ask for the SLES 9 CD #1 using the /yast/order file.
But I had to put it in the top folder of the CD instead of the product
directory where my contents file was located.
I'm mostly there on the SLES 9 portion of the CD.
Now just to get the SLES 10 kernel, initrd, root and my profiles to boot
and ask for SLES 10 CD #1 (currently looking at add on product method).
Thanks
Adam W. Hawks
T/L: 794-4033
Office: 704 594-4033
Steffen Winterfeldt
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. Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Adam Hawks -
Steffen Winterfeldt