On Thu, 2006-04-13 at 07:22 -0700, Don Hoover wrote:
> Ok, I am trying to build my kickstart environment, and
> am a little confused about Errata.
>
> I have been watching the errata and getting emails
> etc. for sometime now and I have noticed that they do
> not reference a particular release such as RHEL4U2,
> they only say RHEL4, RHEL3 etc.
>
> So I am tring to figure out, how should I plan on
> using errata to keep current?
>
> Do errata get rolled into the next update version?
> For instance, will current errata get rolled into
> RHEL4U5? I picked a few erratas, and followed their
> trail via the notices and bugzillas's but they never
> mention if they get rolled into an update or not.
>
Yes, all errata released between updates get rolled into the following
update. Please note there's a small timing caveat. That is an advisory
which goes out a couple of days before a follow-on release will not be
included in the follow-on release.
> Should I have all my systems apply all the errata from
> a seperate yum directory or should I put the errata
> into my distro distro directories (eg put it into
> RHEL4U2, and RHEL4U3 kickstart directories) and then
> redo the comps.xml for those kickstart directories?
>
> Anyone have any insight?
I would just utilize yum to pull in the latest updates unless there's a
reason for you to take the time and effort to roll you're own trees.
- jkt
--
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*
Jay Turner, QE Manager jkt redhat com Red Hat, Inc.
If A equals success, then the formula is: A = X + Y + Z,
X is work. Y is play. Z is keep your mouth shut. - Albert Einstein
Attachment:
signature.asc
Description: This is a digitally signed message part