- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Secure OS Software for Linux
- >
- post-install patching with Red Hat rpms
Secure OS Software for Linux
1752273
Members
5091
Online
108786
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2002 12:20 PM
тАО01-16-2002 12:20 PM
post-install patching with Red Hat rpms
Is there a more efficient way to deal with a large number of Red Hat rpms and their dependencies? After installation I checked the HP security bulletin archive to get up to date on all the security patches that HP recommends for hp-lx. Some bulletins call for retrieving HPTL* tarballs from HP. Other bulletins call for retrieving rpms from Red Hat, and then manually checking each rpm for dependencies at Red Hat's web site. Although this method is okay for individual patches, it is quite time consuming for the large number of rpms called for after an initial install. As time since the creation of the install CD passes, this problem can only get worse.
Two ideas come to mind. Can up2date or Red Hat Network be used to patch those rpms needed from Red Hat? Alternatively, can HP bundle the recommended Red Hat rpms and their dependencies at the same HP site used to retrieve the HPTL* tarballs?
Ala
Two ideas come to mind. Can up2date or Red Hat Network be used to patch those rpms needed from Red Hat? Alternatively, can HP bundle the recommended Red Hat rpms and their dependencies at the same HP site used to retrieve the HPTL* tarballs?
Ala
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2002 02:50 PM
тАО01-16-2002 02:50 PM
Re: post-install patching with Red Hat rpms
Alan, good call.
There really isn't a good way to deal with lots of patches at once. Up2date could handle the job, but is a little slow, and there are issues when a firewall is in place bewteen you and RedHat.
I really like the idea of HP putting their recommendations into a bundle for d/l and inst.
That'd be slick.
There really isn't a good way to deal with lots of patches at once. Up2date could handle the job, but is a little slow, and there are issues when a firewall is in place bewteen you and RedHat.
I really like the idea of HP putting their recommendations into a bundle for d/l and inst.
That'd be slick.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-17-2002 01:23 AM
тАО01-17-2002 01:23 AM
Re: post-install patching with Red Hat rpms
I have written a little perl-script that can check the rpms installed on one system against a directory of update-rpms. It then tells You which ones should be updated. The dependency-check usually just fails for one or two. The nice thing is, that a system can be checked via ssh (using ssh-agent is very very strongly recommended). Using
rpm -U after an scp does the trick. But (if You for example update glibc) don't forget to update Your compartments!
Konstantin
rpm -U after an scp does the trick. But (if You for example update glibc) don't forget to update Your compartments!
Konstantin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP