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:
# Script to setup SLES netinstall source
if [ $# -lt 1 ]
echo "Please provide the path of the new driver as parameter!"
# check if in correct directory!
if [ ! -f suse/CD1/content ]
echo "Error: Looks like wrong directory!"
# remove previous configurations
if [ -d yast ]
rm -r yast
if [ -d boot ]
rm -r boot
if [ -d media.1 ]
rm -r media.1
if [ -f content ]
if [ -f driverupdate ]
# Now we have to move some data around to make this
# a multiple source directory
# first we copy the order directory described above.
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 ]
# 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
cat << EOF > yast/instorder
# final stuff
#cp ../Code/root/root.neu boot/root
chown -R wwwrun:nogroup .
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(a)de.ibm.com, Phone: +49-7031-16-4407; Fax: +49-7031-16-3232
<hal(a)reactivity.c To: suse-autoinstall(a)suse.com
Subject: [suse-autoinstall] example for sles8 + sp3 install server setup?
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.
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com