This document details how to obtain updates for Novell's Open Enterprise Server versions 1 and 2 (OES1 and OES2) running on Linux, and for SuSE Linux Enterprise Server alone (SLES 9 and SLES10). Installation and configuration of SLES 10 and OES2 components differ from that of OES1 and are covered in a single section.

Oxford University has a site licence for Open Enterprise Server products, that is for both OES1 and OES2. It is possible to run SLES without the OES components under this license and still obtain updates under this agreement. Obtaining updates for OES1 and OES2 is different for each version and from SLES products

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

chkconfig rcd

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 be used.

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 account.

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.

2. SuSE Linux Enterprise Server 9

Under the Oxford University NetWare operating systems site licence, University systems are entitled to updates to SuSE Linux Enterprise Server (SLES) without Open Enterprise Server (OES) installed.

Updates to SLES 9 without OES are managed via YaST Online Updates (YOU) rather than via Red Carpet. Originally for SLES 9 the process of allowing people to access these updates direct from Novell was problematic. As a result OUCS set up a local YOU server. This is run on a best effort basis, and can be accessed once you have obtained a code as per instructions for Open Enterprise Server Please email url="mailto:novell-support@oucs.ox.ac.uk">novell-support@oucs.ox.ac.uk with a subject line of SLES Updates if you are considering running SLES in your environment.

2.1. Upgrading from SuSE Linux Enterprise Server 9

It is possible to do an in place upgrade from SLES 9 to SLES 10. Please be aware that whilst this is a possible and supported route, the decision do so is entirely personal. One consequence of performing an in place upgrade is that the former Red Carpet patches and catalogues continue to exist with /var/cache/rcd. To save space the Cache either prior or subsequent to upgrade can be deleted. Though this is not required; SLES 10 only uses ZLM for updates.

3. Open Enterprise Server 2/SLES10

3.1. Installation and Prerequisites

SLES 10 can still be installed as a standalone server, but OES2 components will only run on a SLES 10 server. The installation procedure has changed since OES sp1 OES components may now be installed:

  • at SLES 10 Install time as an add on product
  • by selecting the OES patterns from the YaST installation menu
  • following completion of the SLES 10 install procedure

Whilst it is possible to successfully install OES after completion of the SLES 10 components it may be advisable to install OES at install time to avoid possible version conflicts later.

3.2. Configuring Updates

Before updates can be configured for either method a code is required. The code is entered in the Novell Customer Care applet via YaST. Once this is done Online updates may be run manually or configured to auto update via YaST or Rug.

3.2.1. Configuring Updates Via Rug

This is done in the same way as for the instructions for OES1

3.2.2. Configuring Updates Via YaSt

This is a very simple procedure. Configure Customer Care Centre information, and run the updates either from YaST or using the YOU icon on the desktop.

From YaSt choose Novell Customer Care Centre, after clicking on configure now, the server tries to contact Novell, and starts to build a catalogue, this may take some time. This will allow you to enter your code (previously obtained from Richard Saxton). If you keep the default setting "regularly synchronise with the customer care centre" your catalogue will be kept up to date with infromation about new patches to download.

After entering your code click on the YOU icon (a globe surrounded by red and blue circular arrows) in the task bar. This icon changes to an orange exclamation mark when there are new updates and patches. Clicking on this starts the update procedure.

YOU can also be invoked via the YaSt menu, Automatic Online Update.

3.2.3. Automating Updates

Patching is much smoother and better integrated for both OES 2 and SLES 10 components than previously. Both the YaST (gui) and Rug (command line) methods actually use ZLM; Red Carpet is no longer used. This has lead to greater ease and consistency of patching and updating.

It is recommended that only one interface Rug or YaSt Online Update be used. Running the YaSt Online Update interface through the gui or command line provides a consistent approach to patching, and is the preferred route for both OES2 and SLED 10.

Although both Rug and YOU use the same catalogue files, the method by which how patches were installed is not marked, the catalogue are thus viewed differently by each mechanism. Once a method is chosen therefore it is recommended that only this method is used to avoid possible inconsistencies.