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 d.qureshi@(protected)

 Back
Reply:     1     2     3     4     5     6     7  

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 ?

Dan

>On 1/26/2007 2:43 AM, Aries Star wrote:
> We have servers which have not been updated with patches for quite some
> time (since year 2005). The latest package usually have the following
> dependancy:
>
> "Before applying this update, make sure all previously released errata
> relevant to your system have been applied."
>
>What I didn't mention in my other posting is *why* you need to do this.
>  One of the key reasons is that package foo may have a requirement for
>say package bar.  When you up2date, it will update bar only if bar isn't
>at the version specificied in the dependency.  If the version is okay
>but is missing some critical security fixes, it won't be updated
>automatically.
>
>One other key reason to update all of the previously released errata is
>that the testing for the latest updates is only done against the current
>versions of the packages.  It's totally impractical for Red Hat (or
>anybody else) to test the latest update of the package you're interested
>in against all previous permutations of patches on your system.  They
>simply bring the systems up to date and then test against that set.
>
>This is why you should not attempt to pick and choose which updates to
>apply - even if you think the update may not be relevant to you, you
>should apply them all.  Exceptions may apply to those who really know
>what they're doing...
>
>   .../Ed
>
>--
>Ed Wilts, RHCE, Mounds View, MN, USA
>mailto:ewilts@(protected)
>
>--
>Taroon-list mailing list
>Taroon-list@(protected)
>https://www.redhat.com/mailman/listinfo/taroon-list
>
>

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