Talk:Roberts Quick References
From CoolSolutionsWiki
Contents |
Change log
- 2008-04-29: Added link to ZLM setup guide Cool Solution
- 2008-03-06: Updated QR16 with Xen best practices and links
- 2008-01-21: Added link to ZLM Advanced Patching Cool Solution
- 2007-11-01: Updated QR11 Troubleshooting with howto submit a bug or share information with/without a support contract or subscribtion
- 2007-10-05: Explained the preference of patching versus updating for OES1 and referenced howto's for ZLM patching OES1 in the Discussion section below
- 2007-10-01: Updated ZLM Backup document with ZLM integrity check example
- 2007-10-01: Updated QR11 Troubleshooting with tainted kernel support and debugging reports for LVM, EVMS
- 2007-09-30: Updated QR17 Autoyast XML examples
- 2007-09-28: Updated QR11 Troubleshooting with kernel dump howto's
- 2007-09-26: Added Summary of Linux Data Management and High Availability Features
- 2007-09-23: Uploaded QR9 ZLM (e.g. ZCC timeout correction) plus Example ZLM Backup report
- 2007-09-09: Uploaded QR9 ZLM (added how to get mirror credentials)
- 2007-09-08: Uploaded QR9 ZLM (added ZLM 7.2 IR1 and SLE10 SP1)
- 2007-08-23: Uploaded QR9 ZLM (yup2zlm links, install source catalog) again (version 14 July)
- 2007-07-17: Updated QR17 with SLED mp3, wmv enabling (e.g. Amarok, Kaffeine, Totem)
- 2007-07-14: Updated QR9 ZLM (yup2zlm links) and QR17 Autoyast install sources
- 2007-07-13: Updated QR9 ZLM and QR17 Autoyast install sources
- 2007-06-18: Correction on autoyast LDAP client in 'Deploying SUSE Linux using autoyast' whitepaper
- 2007-06-14: QR3 and QR11 are updated with the ext3 file system on line extension command ext2online /dev/system/lvm
- 2007-06-12: Added QR17 about Automated SUSE Deployments and Updates
Discussion
- Just type your comments here
Q: How to patch OES1 using ZLM?
Thanks for these quick ref, they are very useful. But why did you say in several quick ref card not to use rug up in oes v1? is it an obsolete advise? Because using zlm 7.2 agent on oes v1, "pin" option in rug is not available (remember, you tell to use "rug pin --entire-channel oes" in oes v1). And "rug up" is ok to update oes v1 in our lab using a zlm 7.2.1 server.
A: Summary of Patching OES1
Hi Jean-Baptiste,
You are right about the more or less obsolete remarks, but ...:
(2007-10-05: OES2 released today :-). OES2 Uses rpm's instead of patches. The following does not apply to OES2.)
- Should I update my Open Enterprise Server with individual PSDB files? This linked TID 3000204 explains that OES1 uses patches and not updates (not regular rpm's).
The problem of using updates instead of patches in OES1 only: One patch might be a bundle of rpm's, and a patch might have a pre- and/or post script. Using 'rug up' or the 'Updates-tab' in the GUI would install rpm's without executing the scripts. There is no way to check if the scripts are executed. The administrator is tempted to use the 'suggested updates', but please do not use 'Updates'.
- Patching an OES Linux Server, but this linked document contains (at the moment of this writing) an obsolete remark. ZLM 6.6.2 is not required! An up-to-date ZLM 7.2 server is preferred.
About OES1 Patching using ZLM 7.2 IR1:
- Setting Up the Open Enterprise Server after Installing ZENworks Linux Management
- How to Patch an OES server with ZENworks Linux Management 7 This TID 3738735 explains how to bundle the patches instead of the regular rpm's.
- As long as you are running the latest ZLM code and create a bundle group with all the bundles (patches!) you wish to apply, then ZLM 7.2 IR1 is a good option (and gives you better control and reporting than "rug pin --entire-channel oes"
Hope this helps, Robert
- This page was last modified 00:36, 29 April 2008.
- This page has been accessed 3,634 times.
- About CoolSolutionsWiki
- Disclaimers