Novell has provided an OES channel using ZENworks Linux Management (ZLM) where you can get patches for updating an existing OES Linux server. The following procedure specifies how to access that channel and patch the server using the Red Carpet GUI.
NOTE:If you are unable to patch your server using the Red Carpet GUI, we recommend that you use the command line (rug) procedures to patch the server. See Patching a Server From the OES Channel Using the Red Carpet Command Line (rug).
If you are not already logged in as user root, log in to the server as user root or su to root.
Make sure you have completed the steps in Before You Patch the Server.
Launch the Red Carpet GUI by doing one of the following from the Linux desktop on the server:
Click> > > .
Click> > > > .
When patching after OES SP2:
Click> > > > .
Verify that the OES Update service was added. This service should have been added by default during the OES Linux installation.
The https://update.novell.com/data service URL should display in the Edit Services dialog box.
If no service or an incorrect service is displayed, do the following:
In the Edit Services dialog box, click.
In thefield, type https://update.novell.com/data.
Verify that the OES Service is activated.
The OES Service is activated if the OES channel displays in the Red Carpet Channel Subscription dialog box when you click theicon.
If the service not activated, do the following:
In the Group Activation dialog box, do the following:
Make sure theservice is selected.
In thefield, type the e-mail address that you entered when you received your activation code.
In thefield, type the activation code you received when you purchased the product.
(Conditional) If you see a message indicating: Warning: Invalid channel:'oes', see TID 10098375 “OES Patch Channel Not Visible after Activating Open Enterprise Server”.
Verify that the server is subscribed to the OES channel.
The server is subscribed to the OES channel if the OES channel displays and has a check mark in the check box next to the OES channel name in the Red Carpet Channel Subscription dialog box when you click theicon.
If the server hasn’t previously subscribed to the OES channel, do the following:
In the Red Carpet Channel Subscriptions dialog box, click the check box in the Subscribed column next to the OES channel listing.
If the Patches screen is not displayed, click thetab.
WARNING:When you open the Red Carpet GUI, thetab is selected by default. Do not use the tab or button. Install patches only from the interface you access from the tab in the Red Carpet GUI. If you update from any other area than the tab, you can leave the server in an undesirable state.
The Update tab is included in this utility for use by other products that are updating SLES only.
If you have updated to the latest patches for the Red Carpet utility, the Patches tab and the Not Installed Patches filter are selected by default.
This Patches page lists both OES and SLES patches available for your OES for Linux server.
Select all the patches that have not been installed.
In the Patches menu, select thefilter.
Selecting this filter lists all the patches with a Not Installed status.
Select all the patches that have not yet been installed (Not Installed status) by selecting all the patches (pressing Ctrl+A).
IMPORTANT:If you select any patches that are already installed, the Step 8.button is not active. Make sure you only select patches that have a “Not Installed” status. See
After clicking, all the patches to be installed should be listed in the field with an Install status in the field as shown in the following figure.
The installation process should start. Accept any prompts that are displayed during the download process.
When the download and installation process completes, you should see the following message in the The transaction has completed successfully.dialog box:
When the installation process is complete, click.
To avoid unwanted memory consumption after using the Red Carpet client, enter the following command at the shell command line prompt: rug set max-allowed-memory 40
Continue with Updating Installation Sources Using YaST.