[3563] in SIPB_Linux_Development
Re: Updates to layered install
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Sep 30 22:00:34 2001
Message-Id: <200110010200.WAA28778@egyptian-gods.MIT.EDU>
To: Alex Coventry <alex_c@MIT.EDU>
cc: Linux-Dev <linux-dev@MIT.EDU>
In-Reply-To: Your message of "Sun, 30 Sep 2001 20:02:05 EDT."
<200110010002.UAA02297@nerd-xing.mit.edu>
Date: Sun, 30 Sep 2001 22:00:29 -0400
From: Greg Hudson <ghudson@MIT.EDU>
> I've heard some concerns that a layered install might have trouble
Perhaps this is a terminology issue. "Layered" refers to a stock Red
Hat machine with some or all Athena RPMs manually installed. Such a
machine will have an /etc/athena/version saying "Version Layered," and
can't take Athena updates. Nobody really seems to do this these days
because manually updating RPMs is a drag.
The SIPB install has trouble taking a full update because of a bug in
how it creates the release-rpms file. If you copy in the release-rpms
file, you won't have this problem. I don't know what other concerns
you might have heard about besides general fear of untested
situations.
While I'm here, you should take a look at
/mit/install/rhlinux/installer/phase2 and make sure that for each
thing it does to the machine beyond installing the RPMs, you either do
it or have a reason not to (e.g. because it's taken care of by the Red
Hat install). The SIPB install doesn't disable console logins and
doesn't set PUBLIC=true in /etc/athena/rc.conf, so you don't need to
worry about those.
