[linux-security] RE: check for rpms that should be upgraded

[Richard Blackwell <blackw@sfu.ca>]

Quoting Martin Siegert <siegert@sfu.ca>:

> I was ask the question, whether there is a script/command available
> that would list those rpms/packages on a system that should be upgraded.
>
[snip-o'-rama]
>
> 2) For RedHat there is the up2date package. I have not tried it - on my
> system it requires so many other packages that I choose not to install
> up2date.
> If there is somebody on the list who has used up2date, feel free to
> report your experience to the list.
>
[yet more snipping with wreckless abandon]

I use up2date on two systems here in Psychology, and one at home.  It works
very well.  It is significantly quicker and simpler than updating packages
individually, and it will even install new kernels.

When I first used up2date, I had to register with RedHat Network.  This gave
me full access to the "Software Manager" service via up2date.  Since then I
have registered a number of systems with the Network.  The only drawback to
this service is that unless you fork over some cash to the tune of $20
USD/machine/month, only one of your registered systems can use the up2date
service at one time.  If you want to change the system that gets to use
up2date, you log on to RedHat Network, downgrade the system using the
"Software Manager" and upgrade one of your other systems.  Again, it still
beats installing each package individually, and it does provide
system-specific errata information for each registered machine.

I give it a two-thumbs up.

Now, I also believe that a decent up2date system could be developed here on
campus using local expertise, and Martin has anted up with check-rpms.  Now,
if only someone had the time to take this initiative to the next level:

- package version management,
- multi-version installatin control,
- package dependency resolution,
- kernel installation (with boot disk creation and lilo updating),
- alerting service,
- free

Cheers,
Richard Blackwell