On April 29, 2008, Novell released OES 1 SP2 Updates through the standard oes patch channel. The updates consist of SLES 9 SP4 patches and some OES component patches. This is a channel-only release. There is no physical media available.
The server that is to be patched must be running OES1 SP2, and it must be configured to receive patches through the oes patch channel. For more information on configuring the patch channel, see âPatching an OES Linux Serverâ in the OES 1 SP2 documentation.
IMPORTANT:For servers still running OES 1 SP1, the procedure for updating to OES 1 SP2 has changed slightly due to the SLES 9 SP4 patches that are now in the channel.
Do the following:
Follow the entire procedure outlined in the documentation for either
After completing all the instructions, verify the system dependencies as follows:
At the command line, enter rug ve and then type y to apply any additional packages that are needed
In the Red Carpet GUI, click> (or type Ctrl + D) and apply any needed packages.
The OES 1 server is now running with all supported SLES 9 SP4 patches. No further action is required at this time, but it is recommended to run the patch process regularly to ensure that the latest security and other fixes are applied.
After completing the steps outlined in Section 5.0, Applying OES 1 SP2 Updates and apply all the patches in the channel, the server will be running OES 1 services on the SLES 9 SP4 platform. It really is just that simple.
Novell Support: To retain Novell support, OES 1 servers must be patched only through the oes patch channel. Patching an OES 1 server through a SLES channel is not supported. Refer to TID 3045794 - How To Correctly Patch an Open Enterprise Server Linux for details on the patch procedure.
Third-Party Product Support: Updating an OES 1 server to run on the SLES 9 SP4 base might affect the functioning of kernel-space partner products, such as anti-virus solutions. Before updating, be sure to contact third-party solution providers to ensure that they support SLES 9 SP4.
Samba Gets Sleepy: Samba users whose workstations have been sitting idle for several minutes might be required to reauthenticate when they resume working.
Cluster Split-Brain Detection: Detection still doesnât work properly when the LAN cable is disconnected on a two-node cluster.
NCP Cross-Protocol Locking: This is not functioning as expected when both a Samba user and a Novell Client user attempt to access the same file simultaneously. Rather than opening a read-only copy of the file, the second open request now results in a
Forbidden message, and the user is unable to open the file at all.
To apply OES 1 SP2 Updates to an OES 1 SP2 server, do the following:
Follow the instructions in âPatching an OES Linux Serverâ in the OES 1 SP2 documentation and apply all of the patches in the oes channel.
After applying the patches, click the rug refresh at the terminal prompt to check for additional patches.button or enter
If additional patches are listed, apply them to the server as well.
This will ensure that the server has the latest kernel-update-tool installed.
The OES 1 server is now running with all supported SLES 9 SP4 patches. No further action is required at this time, but be sure to run the patch process regularly to ensure that the server has the latest security and other fixes.
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.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright Â© 2008 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 on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.
- Novell, Inc.
- 404 Wyman Street, Suite 500
- Waltham, MA 02451
- Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell Documentation Web page.
For Novell trademarks, see the Novell Trademark and Service Mark list.
- All third-party trademarks are the property of their respective owners.