First, in an environment where I have multiple RedHat systems of the
same vintage, I keep a NFS shared mirror of the "updates" directories. By
mounting that tree and running 'rpm -F *' (or your favorite shell trick to
avoid clobbering custom packages/kernels/etc), RPM will "Freshen"
installed packages to the latest updated versions. This works well unless
the updates tree is broken (as it all-too-often is).
The up2date utility is (usually) wonderful for a small number of
systems. The worst issue I've seen is that it often breaks in such a way
that it's almost impossible to get working again without an
uninstall/reinstall. The version that 7.0 uses seems to behave better,
plus it has far better progress indicators than 6.2 version had.
One thing that I'd like to see would be the ability to run a local
up2date server. Since most proxies won't cache up2date traffic
(everything comes through with a .cgi URL), updating the same 5MB package
on ten machines results in 50+MB of traffic from a RedHAt FTP. I'd love to
have the client connect to a local mirror instead. Does anyone know if
that's possible?
--
-Matt
Vital papers will demonstrate their vitality by moving from where you
left them to where you can't find them.
On Tue, 13 Feb 2001, Tony Lambiris wrote:
> very true, but its soooooooo much easier to do apt-get -u update, instead of
> downloading all RPM updates, then finding out which RPMs are already installed,
> then installing the associative RPMs. Its a hassle. Although I have heard they
> had a new update utility out called up2date, though I never tried it. Any
> thoughts on this tool?
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
