I would stick with getting the errata packages 'on or near' the update release. The update releases also go through a brief beta cycle where the errata list included would be frozen once the beta was announced/released. Marco RHCE > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Clark, Patricia > Sent: Thursday, September 22, 2005 10:19 AM > To: redhat-list@xxxxxxxxxx > Subject: Errata and update releases > > What is the rule-of-thumb pertaining to applied errata in an update > release? I need to maintain supported systems via sneakernet. I have > the latest updated ISOs for RHEL3 and RHEL4 and want to make > sure that I > have all of the errata packages, too. Can I correctly assume that > anything released since the update is all that I need, or do I need to > additionally obtain errata packages released on or near the update > release? I know I can check these current updates against the errata, > but I want to know for future reference. > > Patti Clark > Unix System Administrator > Office of Scientific and Technical Information > <mailto:clarkp@xxxxxxxx> > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=subscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
