Incorporating SLES-SP2 into an AutoYast installation source?
Can anybody recommend a guide as to how I'd go about incorporating SLES SP2 into a SLES9 repository? I'm about to image a number of servers, and ideally would have them all come up fully patched, and ready to go. -- Michael T. Halligan Chief Technology Officer ------------------- BitPusher, LLC http://www.bitpusher.com/ 1.888.9PUSHER 415.724.7998 (Mobile) 415.520.0876 (Fax)
Michael T. Halligan wrote:
Can anybody recommend a guide as to how I'd go about incorporating SLES SP2 into a SLES9 repository? I'm about to image a number of servers, and ideally would have them all come up fully patched, and ready to go.
Thanks to Jared Ottley for the answer on this one : **************************************** 5.3.1 Integrating the Service Pack into an installation server -------------------------------------------------------------- The YaST2 install server module needs some bugfixes to be able to read and integrate Service Pack CDs. Thus please make sure you have at least version 2.9.21-0.0.1 of yast2-instserver installed (you will find such a newer package on the Service Pack CD itself). Then to the following steps: o Call YaST -> Misc -> Installation Server -> Change -> Edit o Enable the checkbox "Prompt for additional CDs (Service Packs, Additional Package CDs, etc.)" o Hit "Next" button o It will say that contents already exists in this directory o Hit "Ok" button o It will prompt for CD1 o Now insert the "Service Pack CD1" and hit "Continue" o The contents of Service Pack CD1 will be copied to the local disk o Proceed the same way when prompted for CD2 ****************************************** -- Michael T. Halligan Chief Technology Officer ------------------- BitPusher, LLC http://www.bitpusher.com/ 1.888.9PUSHER 415.724.7998 (Mobile) 415.520.0876 (Fax)
Michael T. Halligan wrote:
Can anybody recommend a guide as to how I'd go about incorporating SLES SP2 into a SLES9 repository? I'm about to image a number of servers, and ideally would have them all come up fully patched, and ready to go.
Here's what I did for SLES9.SP1: # create the repository structure cd /repository/install/linux mkdir SLES9.SP1 mkdir SLES9.SP1/sles9 mkdir SLES9.SP1/core9 mkdir SLES9.SP1/SLES9-SP1 # copy the first CD from the iso image in SLES9.ISO mount -o loop SLES9.ISO/SLES9-CD1.iso /mnt/iso cp /mnt/iso SLES9.SP1/sles9/CD1 umount /mnt/iso # copy remaining iso images for i in {1-5}; do mount -o loop SLES9.ISO/SLES9-SP1-CD${i}.iso /mnt/iso cp -a /mnt/iso/ SLES9.SP1/SLES9-SP1/CD${i} umount /mnt/iso done mkdir yast vi yast/instorder /SLES9-SP1/CD1 /sles9/CD1 /core9/CD1 vi yast/order (Tabs!) /SLES9-SP1/CD1 /SLES9-SP1/CD1 /sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1 ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s SLES9-SP1/CD1/driverupdate driverupdate ln -s SLES9-SP1/CD1/linux linux ln -s sles9/CD1/media.1 media.1 -Mike
Aha, I have successfully imaged a server. My method was just to use the gui tool in YAST (actually using gui tools is a new concept for me). I just ran Yast2 -> Misc -> Installation server .. built a new installation server with the isos from SLES9 for x86-64, then followed the directions Jared gave me to add the SP2 isos, and voila, it works. It was a bit too easy. Michael Steinmann wrote:
Michael T. Halligan wrote:
Can anybody recommend a guide as to how I'd go about incorporating SLES SP2 into a SLES9 repository? I'm about to image a number of servers, and ideally would have them all come up fully patched, and ready to go.
Here's what I did for SLES9.SP1:
# create the repository structure cd /repository/install/linux mkdir SLES9.SP1 mkdir SLES9.SP1/sles9 mkdir SLES9.SP1/core9 mkdir SLES9.SP1/SLES9-SP1
# copy the first CD from the iso image in SLES9.ISO mount -o loop SLES9.ISO/SLES9-CD1.iso /mnt/iso cp /mnt/iso SLES9.SP1/sles9/CD1 umount /mnt/iso
# copy remaining iso images for i in {1-5}; do mount -o loop SLES9.ISO/SLES9-SP1-CD${i}.iso /mnt/iso cp -a /mnt/iso/ SLES9.SP1/SLES9-SP1/CD${i} umount /mnt/iso done
mkdir yast
vi yast/instorder /SLES9-SP1/CD1 /sles9/CD1 /core9/CD1
vi yast/order (Tabs!) /SLES9-SP1/CD1 /SLES9-SP1/CD1 /sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1
ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s SLES9-SP1/CD1/driverupdate driverupdate ln -s SLES9-SP1/CD1/linux linux ln -s sles9/CD1/media.1 media.1
-Mike
-- Michael T. Halligan Chief Technology Officer ------------------- BitPusher, LLC http://www.bitpusher.com/ 1.888.9PUSHER 415.724.7998 (Mobile) 415.520.0876 (Fax)
participants (2)
-
Michael Steinmann -
Michael T. Halligan