[rhn-users] RHN: best practise kernel updates

[Daniel Wittenberg]

My general practice is to still do the kernel manually, because I like
to make sure the grub.conf and device.map are ok, since I've seen both
not get updated right before.  So generally for kernels I just login and
do an up2date --update --force after everything else is done, and that
will update the kernel.

Dan

On Thu, 2005-02-10 at 11:18 +0000, Daryl Field wrote:
> Hi, I'd like to ask what you all consider to be the best practises when 
> updating kernels on rhel3 boxes.
> 
> We exclude kernel updates via /etc/sysconfig/rhn/up2date - which I 
> assume to be the default.
> 
> One thing that bothers me - because we do this - every system listed on 
> the rhn web interface shows that updates are required, red excamation 
> mark. This means I have to check each group/system to see wether an 
> actual package is outdated or its just the kernel business. An 
> inconvenience for sure.
> 
> So back to kernel updates - download the rpm manually, -ivh it, then 
> check grub and /boot seems to be the rh manual approach. I'd be very 
> interested to know how you all approach this.
> 
> Daryl

-- 
=============================
Daniel Wittenberg
RHCE/IBM Certified Specialist
President/CTO
The Starken Group
http://www.starken.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/rhn-users/attachments/20050210/3cc89681/attachment.sig>