From: John Moylan (john at domain rte.ie)
Date: Thu 26 Sep 2002 - 16:42:03 IST
Build a seperate repository per minor version on an NFS mounted drive
(making sure to purge kernel RPM's and RPM's whose sigs are not valid.)
then rpm -Fvh from the appropriate reposititory per machine.
This is a good link with some scripts for building custom repositories.
You can't just do a wget on all of the files in
ftp.esat.net/updates.redhat.com because multiple updates are stored in
the same directories on that site, cutting and purging is necessary.
With your own repository, it is possible to package your own rpm's and
pop then into the apropriate directory also.
If you are updating to a major version, then start from scratch, or,
better still.. write a kickstart script with a post section which tweaks
to your liking.
John
David Malone wrote:
>>You'll have to force it, and stuff will break. I don't recommend doing
>>this at all.
>>
>>
>
>Doesn't sound much worse than what the redhat installer did when I
>tried updating from 6.2 to 7.1. Though, if it had told me that this
>wasn't a recommended course of action I might have thought twice ;-)
>
>How do you do remote upgrades?
>
> David.
>
>
******************************************************************************
The information in this e-mail is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this e-mail by anyone else
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution, or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful.
Please note that emails to, from and within RTE may be subject to the Freedom
of Information Act 1997 and may be liable to disclosure.
******************************************************************************
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:19:06 GMT