 | | Re: RHN icon problem [this response is regarding the CAN-2005-1263
question] | Re: RHN icon problem [this response is regarding the CAN-2005-1263
question] 2005-05-12 - By Stephen Gardner
Back
On Thu, 12 May 2005, bob wrote:
> Question in the meantime, does everyone else use up2date for there kernel
> upgrades or the majority ?
> On my slackware boxes i install them manually so when this bug came out i
> just patch -p0 >>
> With this backported kernel can you do the same? Ive only ran this redhat box
> for over 2months now just
> now getting the hang of it, Havnt seen a redhat box since 5.1 oh the changes
> =)
>
> -bob
Bob,
Unless you have a lot of time it's unlikely that you can maintain a
sustainable patch set against the RHEL kernel. The RHEL3 v2.4.21-27.0.4
source has (approximately) 1.24 million lines of source code changes
(that may include the same line being changed multiple times, 198,819
diff lines removed, 1,046,023 diff lines added) from the v2.4.21 baseline
kernel. The chances that patches designed for the baseline kernel
will apply cleanly to the RHEL3 kernel source tree are possible but there
could be unexpected knock-on affects. There's nothing to say you can't or you
shouldn't do your own patching just that you will need to read the patches
and understand the kernel source (+ the RHEL diffs) to produce clean and
appropriate updates.
Reading the changes to the Bugzilla report this particular security
problem can be combatted to a large extent with a temporary workaround by
include "ulimit -c 0" early in the system start-up scripts (eg
rc.sysinit).
Regards,
Stephen
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
Earn $52 per hosting referral at Lunarpages.
|
|
|