When I use this script (slightly modified as I don't have Addons or suplementary CDs), it seems to set it up OK, and it boots OK, but when it actually comes to do the install I get the following: Please insert 'UnitedLinux 1.0 Service-Pack Version 3' CD 1 SuSE Linux AG != SuSE Linux AG 20021022150203 != 20031106141452 It's clearly got both the vanilla original and the SP3 CD images in the installation pane behind this message. Investigation revealed that it was parsing the file media.1/media from the root of the installation tree (/foo/suse/dev in my case), and that it was expecting to find the SP3 media.1/media file. I manually switched it and it chuntered for a bit, didn't do anything and then came back asking me to insert the 'UnitedLinux Version 1.0' CD 1. What is wrong, and how can I fix it to see and use all the original and SP3 CDs? For the record, I'm using PXE to boot and am using the original CDs kernel and initrd (just tried the SP3 ones and was the same as expected). Is there any documentation anywhere on how to lay out the installation tree? Are these the sort of questions the SuSE technical support will be able to answer, as I'm on a tight schedule to get this working... :-( Tom ----- Original Message ----- From: "Joachim Jordan" Cc: Sent: Wednesday, January 14, 2004 8:38 AM Subject: Re: [suse-autoinstall] example for sles8 + sp3 install server setup?

Hi everyone,

it works for me to it that way. I added the SP3 just as another source to the installation tree.

Here is my script i'm using to setup the distribution: ------------------------------------------------------- #!/bin/sh

# Script to setup SLES netinstall source if [ $# -lt 1 ] then echo "Please provide the path of the new driver as parameter!" exit 1 fi cd $1

# check if in correct directory! if [ ! -f suse/CD1/content ] then echo "Error: Looks like wrong directory!" exit 1 fi

# remove previous configurations if [ -d yast ] then rm -r yast fi if [ -d boot ] then rm -r boot fi if [ -d media.1 ] then rm -r media.1 fi if [ -f content ] then rm content fi

if [ -f driverupdate ] then rm driverupdate fi

# Now we have to move some data around to make this # a multiple source directory # # first we copy the order directory described above. mkdir yast cp suse/CD1/content yast/ cp suse/CD1/content .

# Then the boot directory with the installation image cp -a suse/CD1/boot .

# The content file and the media directory cp -a suse/CD1/media.1 . if [ -f media.1/info.txt ] then rm media.1/info.txt fi

# Now we copy the description files from SLES to the order directory as # described earlier. mkdir -p yast/suse/suse/setup/descr cp -a suse/CD1/suse/setup/descr yast/suse/suse/setup cp suse/CD1/content yast/suse/ cp -a suse/CD1/media.1 yast/suse/ cp -a suse/CD2/media.2 yast/suse/ cp -a suse/CD3/media.3 yast/suse/

# Same applies for supplementary mkdir -p yast/sup/suse/setup/descr cp -a supplementary/CD1/suse/setup/descr yast/sup/suse/setup cp supplementary/CD1/content yast/sup/ cp -a supplementary/CD1/media.1 yast/sup/ cp -a supplementary/CD2/media.2 yast/sup/

# Do the same for Service Pack 3 mkdir -p yast/sp3/suse/setup/descr cp -LRp sp3/CD1/suse/setup/descr yast/sp3/suse/setup cp sp3/CD1/content yast/sp3/ cp -a sp3/CD1/media.1 yast/sp3/ cp -a sp3/CD2/media.2 yast/sp3/ # overwrite the old file in the boot directory with new ones cp -a sp3/CD1/boot . # copy driverupdate file cp sp3/CD1/driverupdate .

# Do the same for Addons mkdir -p yast/ad/addons/setup/descr cp -a Addons/addons/setup/descr yast/ad/addons/setup cp Addons/content yast/ad/ cp -a Addons/media.1 yast/ad/

# We are almost done.. # Now we'll adapt the order files. # Fields of the order files are TAB delimited

cat << EOF > yast/order /yast/ad Addons /yast/sp3 sp3/CD1 /yast/suse suse/CD1 /yast/sup supplementary/CD1 EOF

cat << EOF > yast/instorder /yast/sup /yast/suse /yast/sp3 /yast/ad EOF

# final stuff #cp ../Code/root/root.neu boot/root

chown -R wwwrun:nogroup .

# End ------------------------------------------------------------------- I even added another source for my own packages. For that i reused the

content and media.1 files from the SLES distribution and changed them.

I'm using HTTP as installation protocol and this is for an Power PC based installation for JS20 blades. But it is more or less the same for Intel.

Just one thing about the SP3, to get all the Yast fixes included in the installation process( for example necessary for HTTP support, HTTP is broken in the SLES8 and fixed with the code in the SP3), you have to copy the driverupdate file to the root of your new multi source distribution(or if you use NFS, you can also copy the subdirectory containing all from the CD to the root).

For me, the driverupdate file does not work. If i use it, yast dies in the middle of the installation with an segfault. If i copy all files from the driverupdate file into the root file manually, it works.

Best regards, Joachim Jordan

Linux IT Architect, EMEA Linux Center of Competence IBM Laboratories, Dept.3300, Schoenaicherstr.220, D 71032 Boeblingen, Germany Sametime/e-mail: jordanj@de.ibm.com, Phone: +49-7031-16-4407; Fax: +49-7031-16-3232

Hal Wine cc: Subject: [suse-autoinstall] example for sles8 + sp3 install server setup? 13.01.2004 18:32

Can anyone point me to an example install server layout for autoyast installations of sles 8 + service pack 3?

I followed Anas' example laytout for my original installation server setup.

I'ts unclear to me if I should: 1) replace the sles8 cd content with the content from sp3 cd's, or 2) add sp3 content as another source.

If #2, I think I would place it at the end of the order file, and the beginning of the instorder. Is that correct?

Finally, what do folks typically do to handle maintenance updates? I.e. where do they place the RPMs.

Thanks, --Hal

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com