Automating Red Hat updates (was Re: A call for recomendations and helpful some advice)

[John Abreau]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Cole Tuininga <colet at code-energy.com> writes:

> There's an assumption being made in this suggestion however.  That is
> that I can safely nfs export to the systems in question.  Unfortunately
> they are kind of scattered across the net, and having a system with an
> open portmap and nfs server doesn't thrill me.  

rpm can use http urls in place of filenames, so you could always just 
share them with apache instead of nfs. Of course, you won't have filename 
globbing, so it will be slightly more complicated to implement; instead of

    rpm -Fhv .../updates/i386/*.rpm

you could first generate a list of urls 

    curl --silent http://server/.../updates/i386/ | sed -e '!/<A HREF/d' \
        -e 's/.*<A HREF="//' -e 's/".*//' -e '!/\.rpm$/d' > LIST

and then pass that to rpm 

    rpm -Fhv $(cat LIST)


- --
John Abreau / Executive Director, Boston Linux & Unix
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Exmh version 2.6 02/09/2003

iQCVAwUBPoEs3FV9A5rVx7XZAQKAZAP/WCAzp3mCKZiDD5vBmJwrJZ7vMu26YwlW
UN/+TzMaZoY+IlEVBbZBMgcoeM1LlqIEXawiyGbXKBp5j+hxaz1d9Kjuvi11A8eb
UYp77A0A8uXfQRWpgVDmmAD/77yIopTkSX0IRDHux3WtMhyQd3PkBioJmK1qfAzw
Jixy0DCOqI4=
=4hZS
-----END PGP SIGNATURE-----