SUSE LINUX Enterprise Server 9 SP 3
Download and Installation
checking MD5 values of downloaded files
To verify downloaded file integrity,
you must check each file's MD5 values by doing one of the following:
- On a Linux system at the shell prompt, enter the following
command:
md5sum filename
where filename is the name of the file you are
verifying.
- On a Windows system, obtain a Windows-compatible MD5-based
checksum utility from the Web and follow the usage instructions for the
utility.
Install Notes for SUSE LINUX Enterprise Server Service Pack:
Overview
1. Important General Information
2. Updating from SLES GA or Older Service Pack to the Current One
2.1 Using the CD Autorun Mechanism
2.2 Calling YaST2 Manually or Remotely
2.3 Updating Functional Patches
2.4 Registering the Service Pack as an Additional
Installation Source
2.5 Updating Individual Packages
2.6 Using Multiple Kernels
2.7 Updating Everything Using "System Update"
2.8 Updating to a Service Pack Using "Patch cd
update"
3. Fresh Installation Using a Service Pack
3.1 Need For
3.2 Using the Bootable SP CD
3.3 Setting Up an Installation Server
3.3.1
Integrating the Service Pack into an Installation Server
3.4 Using Special Installation Images
4. More Information and Feedback
1. Important General Information
These installation notes are generic for all SLES-based products, so
some parts
may not apply to a particular architecture or product. In cases where
this is
not obvious, the architectures are explicitly listed.
2. Updating from SLES GA or Older Service Pack to the Current
One
Important Note:
-----------------------
After completing any form of update, look at the contents of the file
/var/adm/rpmconfigcheck. This file contains a list of configuration
files
that could not be updated automatically. Usually this means the
installed
version was modified. These files must be checked and the
configurations
adjusted manually.
2.1 Using the CD Autorun Mechanism
The most convenient way to update your system to a Service Pack is to
use
the CD autorun feature. Log in to KDE and insert the Service Pack CD1.
After
some seconds, a window prompts for the root password (in case
you are logged in as a regular user) and offers to install the patches
from this CD. You can either install all recommended updates (this is
the
default) or select individual updates. This is basically the same
update
method as described in 2.3, so continue to
read there for more details. Do not forget to reboot at the end.
2.2 Calling YaST2 Manually or Remotely
The autorun of chapter 2.1 might not be an option if you have to update
machines remotely or even without a CD-ROM drive. In this case,
start YaST manually as the superuser root with the command "yast2".
Then select the respective YaST module as mentioned in any chapter
below.
A YaST2 reference like "Software -> Patch CD Update" means that
you
should select "Software" on the left side then the "Patch CD Update"
icon on the right side.
To use YaST remotely, login via ssh with
ssh -X root@<YOUR_MACHINE>
then call "yast2". See also chapter 4 for references to our manuals
and documentation, including sophisticated other methods to call and
use
yast, like via VNC or a serial line.
2.3 Updating Functional Patches
The maintenance updates to SLES are grouped into logical functional
units,
called "patches", which are (or will be) available via the maintenance
Web,
but also available on this Service Pack. This method is much more
convenient
and less error-prone than updating packages individually and also
supports
special hooks for PRE and POST scripts of a complete patch. This method
can be used calling YaST -> Software -> Patch CD Update.
Although it
was designed for CDs initially, it can also be used via many other
sources, like NFS or a local directory.
There are four classes of patches. First, there are patches to YaST
itself.
These are always selected and must be installed first. Second, there
are
security patches, which should always be installed. Third, there are
recommended patches, which usually should be installed. Check the
indications and contraindications for these. Last, there are optional
patches, which are only needed in very special cases.
View details for a patch by clicking 'Description'.
If additional information or warnings are available for any packages
selected for installation, YaST2 shows those in pop-up message
windows during the installation process. Do not ignore these
messages, because they contain important information for your system.
Usually the right patches for your system are automatically selected,
so in most cases you can just accept the defaults.
If one of the pop-up screens said a reboot
is necessary, reboot now.
2.4 Registering the Service Pack as an Additional
Installation Source
For the YaST package manager to know about the updated packages
residing on the Service Pack CD, you must register this CD as an
additional installation source.
You can do this in YaST -> Software -> Change Source of
Installation.
Select "Add" and "CD" then use the "Up" button to move the
Service Pack to the top (highest priority). This makes sure that
if a newer version of a package is found on the Service Pack CD,
this version is used.
2.5 Updating Individual Packages
First register the Service Pack as an additional installation
source (see Section 2.4). Then you can use the "Install and Remove
Software"
module of YaST to update, install, or remove individual packages.
2.6 Using Multiple Kernels
It is possible to install multiple kernels side by side. This feature
is meant to allow administrators to upgrade from one kernel to another
by installing the new kernel, verifying that the new kernel works as
expected, then uninstalling the old kernel. While YaST does not yet
support this feature, kernels can easily be installed and uninstalled
from the shell using rpm -i <package>.rpm. For
information about managing
packages from the command line, refer to the Administration Guide.
The default boot loader menus contain one kernel entry. Before
installing
multiple kernels, it is useful to add an entry for the extra kernels,
so
that they can easily be selected. The kernel that was active before
installing
a new kernel can be accessed as vmlinuz.previous and initrd.previous.
By
creating a boot loader entry similar to the default entry and having
this
entry refer to vmlinuz.previous and initrd.previous instead of vmlinuz
and
initrd, the previously active kernel can be accessed.
2.7 Updating Everything Using "System Update"
You first need to register the Service Pack as an additional
installation
source (see Section 2.4). Then you can update all packages with
the
"System Update" module of YaST.
2.8 Updating to a Service Pack Using "Patch CD Update"
When updating to a Service Pack by means of a "Patch CD Update" and a
network installation source, it is necessary to copy the *contents* of
all Service Pack CDs into one directory then use this directory as
that source.
3. Fresh Installation Using a Service Pack
If you are doing a fresh installation, you can benefit from a
Service Pack as well. Find architecture-specific information at
http://www.novell.com/documentation/sles9.
Enhancements in the installer are listed in Section 2.1 of the NEWS
file.
3.1 Need For
If you have already successfully installed SLES GA or with a Service
Pack,
there is no need to do a fresh install. Just use any of the
update mechanisms described in Chapter 2 to get your system to the
latest
Service Pack level.
In cases where the SLES GA or older Service Pack version did not
work for you, either because of missing hardware support or bugs in the
installer you should try a fresh install with the latest Service Pack
using any of the methods listed below.
3.2 Using the Bootable SP CD
Insert the bootable Service Pack CD1 in your drive and boot your
machine.
The kernel loads and the following dialog appears:
"Make sure that CD number 1 is in your
drive."
At this point, insert the first product CD, in this case, CD1 of the
SLES GA ISO set. Hit "Ok" and the regular installation (with the new
kernel, drivers, and the new YaST) runs. Continue as usual with the
installation.
The benefit of this method is that you will directly install the newest
version of every package in this mode, so there is no need to call any
of the
update methods listed above afterwards.
If you have to install many machines we recommend booting from
Service Pack CD1 but using a network installation server.
Chapter 3.3 explains how to set up an installation server.
3.3 Setting Up an Installation Server
Here is a step-by-step guide to setting up a SLES
installation
server. This example sets up an NFS installation server, but the
method for others, like HTTP or FTP, are very similar.
o Select YaST -> Misc -> Installation Server
o Select "Configure as NFS Source" and, as "Directory", the
desired
location. This example uses "/install".
o Then click "Next".
o Leave the defaults for "Host Wild Card" and "Options".
o Click "Next".
o With this, an NFS server serving "/install" is set up automatically.
o The "Source Configuration" dialog appears.
o In "Sources to Configure", click "Configure".
o As "Source Name", enter the desired name for this
installation
source, for example, "sles9". This creates a subdirectory
"sles9"
under /install.
o Enable "Announce as Installation Service with SLP"
This makes this server broadcast itself as an installation
server and any SUSE product can automatically find it in SLP
install mode.
o If you have CDs of SLES GA and this Service Pack, skip the
next step.
o If you have ISO images instead of CDs, enable this
check box and browse via "Select Directory" to the directory
that contains all ISO images of all CDs.
o Click "Next".
o You will now be prompted to insert "CD1".
o Insert "SLES 9 CD1" (which is the main product CD) and press
"Continue". Now the data from CD1 is copied to the
local directory, in this example, /install/sles9.
o Proceed the same way when prompted for CD2 through CD6.
o Press "Finish".
o Now your installation server for SLES is ready.
o The directory structure should look like this:
/install/sles9/
SUSE-CORE-Version-9/
CD1/
CD2/
CD3/
CD4/
CD5/
SUSE-SLES-Version-9/
CD1/
boot
-> SUSE-SLES-Version-9/CD1/boot
content
-> SUSE-SLES-Version-9/CD1/content
control.xml -> SUSE-SLES-Version-9/CD1/control.xml
media.1
-> SUSE-SLES-Version-9/CD1/media.1
yast/
instorder
order
You may have noticed that the 6 CDs actually are 1 SLES CD,
which is really defining the product settings, and
5
CORE CDs, which contain the common code base for SUSE
business
products (the common code base avoids ISVs or IHVs have
to do multiple certifications).
o Now you can easily install another machine over the network
using the installation server.
o Boot the machine to install from
Service Pack CD1.
o On the initial dialog, scroll one line
down and choose "Installation".
o In the "Boot Options" field, enter
"install=slp" (or change
this with "F3" if this is
available on your platform).
o The machine boots then shows a
selection of
install options it has found
via SLP.
If this does not work out of the box,
you probably
lack a working DHCP and DNS server in
your network.
In this case, use the following
parameter in the "Boot Options":
install=nfs://<IP_ADDRESS_OF_YOUR_SERVER>/install/sles9
to force the installation to use a
certain install server.
3.3.1 Integrating the Service Pack into an Installation Server
The YaST2 install server module needs some bug fixes to be able to read
and integrate Service Pack CDs. Make sure you have at least
version 2.9.20-0.2 of yast2-instserver installed (this package is
on the Service Pack CD itself).
Then follow these steps:
o Call YaST -> Misc -> Installation Server ->
Change -> Edit.
o Enable "Prompt for Additional CDs (Service Packs, Additional Package
CDs, etc.)".
o Click "Next".
o It says that contents already exist in this directory.
o Click "Ok".
o It prompts for CD1.
o Now insert the "Service Pack CD1" and press "Continue".
o The contents of Service Pack CD1 are copied to the local disk.
o Proceed the same way when prompted for CD2.
3.4 Using Special Installation Images
If you cannot boot from CD, find corresponding floppy images
for boot and modules floppies under /boot on CD1.
4. More Information and Feedback
Also read the READMEs on the CDs. Find a summary of most
changes
and fixes in the NEWS file on the Service Pack CD1. Get the very
detailed
changelog information about a particular package from the RPMs
themselves
with
rpm --changelog -qp <FILENAME>.rpm
where <FILENAME>.rpm is the name of the rpm.
The file "ChangeLog" in the top level of CD1 contains a chronological
log of
all the changes that were made for these updated packages.
Find a lot more useful information in the directory "docu"
of CD1 of the original SLES GA CDs. This includes PDF versions of
the SLES installation and administration manuals, which explain many
other sophisticated methods to install and use SLES, for example, using
AutoYaST or VNC.
http://portal.suse.com/sdb/en/2005/04/sles_multipathing.html
describes how to set up and use multipathing.
Visit http://www.novell.com/linux
for the latest Linux product news
from SUSE and Novell.
legal notices
Disclaimer, Export Notice,
Copyright, and Patents
Novell, Inc. makes no representations
or warranties with respect to the contents or use of this
documentation, and specifically disclaims any express or implied
warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and
to make changes to its content, at any time, without obligation to
notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no
representations or warranties with respect to any software, and
specifically disclaims any express or implied warranties of
merchantability or fitness for any particular purpose. Further, Novell,
Inc. reserves the right to make changes to any and all parts of Novell
software, at any time, without any obligation to notify any person or
entity of such changes.
You may not use, export, or re-export
this product in violation of any applicable laws or regulations
including, without limitation, U.S. export regulations or the laws of
the country in which you reside.
Copyright (C) 2005 Novell, Inc. All
rights reserved. No part of this publication may be reproduced,
photocopied, stored on a retrieval system, or transmitted without the
express written consent of the publisher.
Novell, Inc. has intellectual property
rights relating to technology embodied in the product that is described
in this document. In particular, and without limitation, these
intellectual property rights may include one or more of the U.S.
patents listed at
http://www.novell.com/company/legal/patents/ and one or more
additional patents or pending patent applications in the U.S. and in
other countries.
Novell Trademarks
Novell and NetWare are registered
trademarks of Novell, Inc. in the United States and other countries.
Third-Party Trademarks
All third-party trademarks are the
property of their respective owners.