[3562] in SIPB_Linux_Development
Re: Updates to layered install
daemon@ATHENA.MIT.EDU (Alex Coventry)
Sun Sep 30 20:37:15 2001
Date: Sun, 30 Sep 2001 20:37:10 -0400 (EDT)
Message-Id: <200110010037.UAA05282@nerd-xing.mit.edu>
From: Alex Coventry <alex_c@MIT.EDU>
To: sly@MIT.EDU
CC: linux-dev@MIT.EDU
In-reply-to: <200110010006.UAA14414@tomcat.mit.edu> (message from Angie Kelic
on Sun, 30 Sep 2001 20:06:58 -0400)
Yeah, part of the layered installl script removes all the rpm's not on
the control list, so rpm -qa gives exactly the same list as it would on
a cluster machine, and it adjusts the /var/athena/release-rpms file
accordingly, so hopefully it's not subject to those sorts of update
problems.
Alex.
>>>>> "Angie" == Angie Kelic <sly@MIT.EDU> writes:
Angie> The way I've seen layered installs fail with redhat version
Angie> updates is that the stock RedHat install has rpms in it that
Angie> the athena release does not have. Athena expects only the
Angie> rpms listed in /etc/athena/release-rpms to be installed.
Angie> These 'extra' rpms will never get removed since the athena
Angie> updates don't generate a complete listing of rpms installed
Angie> on the machine to compare to the list of release-rpms. In
Angie> many cases these rpms do not cause conflicts with minor
Angie> athena updates but can and do with release version updates.
Angie> If you do a comparison of rpm -qa and the control list of
Angie> rpms when the install runs and cledan up the rpms that are
Angie> 'extra' from teh stock install, you shouldnt run into the
Angie> update issues that tpyical layered machines see.
