On Sat, Aug 10, 2002 at 12:13:45PM -0230, Mike Pelley wrote:
> Folks,
>
> I've just bollock'ed a nicely-running 7.0 system. I ran up2date and it
> came up with the new version of BIND to be installed as being
> 9.2.1.0.70.2. Fine, that's seems like a good update for a buffer
> overflow issue. So, I run it.
And you apparently didn't see or ignored the standard section in all Red
Hat announcements that all prior updates must be applied first (Section
4 - Solution). That said, I'd say that Red Hat has a bug in their
packaqe - a dependency check should have been done to prevent you from
shooting yourself in th efoot.
> What do I have to do to modify /etc/rc.d/init.d/named to run under the
> 2.2.16-22 kernel?
That's the wrong answer. You should upgrade the kernel. After all,
perhaps another package will come out next week that also causes you
grief. Until you meet the requirements for future updates (all prior
relevant updates must be applied first), your system is effectively
frozen at its current release levels.
> My record with recompiling the kernel is only about 30% success, so I
> don't want to go down that route unless I absolutely have to. I've run
> up2date on the kernel on other systems with success (this is a generic
> HP NetServer LD Pro, nothing special at all - no software RAID, etc), so
> any opinions (asbestos flame suit - purist will say do a recompile,
> uggghh)?
My recommendation is to use up2date to update the kernel - you don't
need to recompile. Just make sure everything else is up to date first,
especially up2date. Once you've got an updated kernel, you're off to
the races. Do *not* delete the current kernel - you'll need it if for
some reason the latest kernel doesn't work for you.
.../Ed
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
Member #1, Red Hat Community Ambassador Program
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
