Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Installation - Getting started with Red Hat Linux
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
Subject: application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
Subject: X Windows problem (xauth)
Subject: Upgrading openoffice 1 1 rpm
Subject: FTP: connection refused
Subject: FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
Subject: broadcom network interface
make mrproper
Couldn 't open PID file /var/run/named/named pid Permission denied
sendmail configuration on redhat
kernel 2 6 and /dev/sound/mixer not found
Subject: Promise 378 controller
Subject: Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
Subject: Lotus Notes under Wine
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
/etc/security/limits conf question
Intel E/1000 driver
rpm database corrupt
Command stream end of file while reading
qla2300 modules
 
up2date - package update dependency

up2date - package update dependency

2007-01-26       - By Ed Wilts

 Back
Reply:     1     2     3     4     5     6     7  

On 1/26/2007 11:23 AM, d.qureshi@(protected) wrote:
> I have several servers that need to be patched with RHEL AS 3 and its been a
long time
> since up2date was run on them.
> I need to catchup with the latest erratas.
>
> I have registered my RHEL AS 3 servers with RHN and for each server there are
loads of
> erratas that need to be applied.
>
> So basically one should apply all erratas to each server using up2date -u ?

Yes.  I typically check to see what is new first, apply the non-kernel
updates with -u, and then finally update the kernel packages with a -uf.
 Then reboot (for the kernel).

Hopefully I don't need to say it but:
1. Ensure you have a good backup or a backout plan.  If you don't, make
sure your resume is not on that server.
2.  Test following your updates, especially if you have a lot of
backlog.  If you stay on top of them, it's easier to identify a package
that caused you an issue, if there was one (hasn't happened to me yet,
but that doesn't mean it won't in the future).

  .../Ed

--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts@(protected)

--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list