1. Open Enterprise Server 1
Please note that these instructions in this section are only relevant to Open
Enterprise Server running on SuSE Linux Enterprise Server (OES1/SLES9). They do not
apply to Open Enterprise Server running on NetWare (OES/NetWare), or to installations
of SLES without OES (for which, see below).
1.1. Installation and Prerequisites OES1/SLES9
OES1/SLES9 is no longer available for download from the evaluation site, but from
the Novell download site, for which you will need a portal login.
Once installed you will need to configure the product in order to obtain updates.
For OES1/SLES9, updates are obtained direct from Novell using Red Carpet, rather
than via the YaST Online Updates used by a pure SLES installation.
Be aware that it is quite possible to install OES/SLES in such a way as to break
updating. If you accepted the default software installation type of OES, you
should be safe. However, if you changed the default type, or made alterations to
the packages being installed, you could have problems. You should check that the
following components are installed, and if any are missing, install them.
- rcd (daemon)
- rug (command line interface)
- red carpet (gui interface)
- oes-release package
If you have to install the Red Carpet components, you also need to make sure that
rcd is set to automatic startup. You can check this via
and if this is off, change startup to automatic via
chkconfig -a rcd
1.2. Automating Updates
In order to download and install updates automatically, you can use cron to
schedule the update using the following command.
rug update -y oes
The cron job should run as root.
1.3. Installing Service Packs
Service packs cannot be installed via Red Carpet. Instead, the OES+SP CDs should
1.4. Configuring Updates
Once you have checked that the Red Carpet components are installed and active, you
will need a code. This is currently available from the ITSS
restricted facilities pages. This code may only be used on systems owned
by Oxford University departments, colleges and other units.
The instructions for configuring access to patches are currently available from
Novell here. Note that the location does change periodically (e.g. after a
service pack). If they have disappeared, go to the OES documentation index
page instead and look for an entry such as "Updating OES Software" or
"Patching a Server Using the ZLM Channel from the Command Line (rug)". As you
follow the instructions, at some point you will need to activate the oes update
channel. This is done via the command
rug act -s service_list_number activation_code email_address
The service_list_number will be 1, and the email_address should be a valid email
address that can be used to contact you. However, it does not actually matter what
the email address is, and it does not have to be linked to a Novell or SuSE portal
Note that all Novell documentation, TIDs etc. that refer to updating OES,
currently do not recommend using the Red Carpet GUI. In fact, in OES SP1, only the
command line interface is supported.
Once you have activated the update channel, follow the Novell instructions to
subscribe to the oes channel and to list, download and install patches.
Up: Contents Next: 2. SuSE Linux Enterprise Server 9