up2date - package update dependency 2007-02-01 - By Guy Waugh
Back
Hi all,
Ed Wilts wrote:
> On 1/26/2007 11:23 AM, d.qureshi@(protected) wrote:
>> 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 ?
>
> Yes. I typically check to see what is new first, apply the non-kernel
> updates with -u, and then finally update the kernel packages with a
> -uf. Then reboot (for the kernel).
>
> Hopefully I don't need to say it but:
> 1. Ensure you have a good backup or a backout plan. If you don't,
> make sure your resume is not on that server.
8-) Good thought re: the resume...
I'm facing this situation at the moment. We can update most of our
systems without having to have major service outages, but a few critical
machines (database/NFS servers etc.) need well-publicised outages for us
to apply updates.
This has got me thinking that if, by some bizarre chance, the updates
break software on the servers and I have to roll back to previous
versions, what would be the best way to do that? I'm thinking either:
* Go to backup tape and restore the entire operating system, or at least
all the files owned by the packages that have been upgraded (would need
a separate exercise to list all the files owned by the updated
packages). Not sure if this would work that cleanly. Alternatively,
* Force-install the old packages over the top of the new packages. Not
really sure if this would work that cleanly either...
Does anyone have any thoughts on these ideas, or other ideas that may be
appropriate for rolling back from RPM upgrades?
Thanks in advance,
Guy.
<snip>
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
