[3655] in SIPB_Linux_Development
Re: Doc out of date
daemon@ATHENA.MIT.EDU (Greg Hudson)
Sun Mar 17 10:27:23 2002
From: Greg Hudson <ghudson@MIT.EDU>
To: Angie Kelic <sly@MIT.EDU>
Cc: linux-dev@MIT.EDU
In-Reply-To: <200203170631.BAA10792@wolverine.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 17 Mar 2002 10:27:16 -0500
Message-Id: <1016378836.1356.50.camel@error-messages.mit.edu>
Mime-Version: 1.0
On Sun, 2002-03-17 at 01:31, Angie Kelic wrote:
> I believe the information that you quote is entirely
> incorrect. I think this didn't actually make it into
> the 8.x release, but into a 9.0.x release. Greg can confirm
> or deny this...
Deny. What I said was correct. And with your fixes to the installer so
that it doesn't install broken-8.4.25, people should be able to update
to 9.0 just fine without Hesiod info. If you have empirical evidence to
the contrary, do tell, but there's no theoretical reason to believe it
won't work.
(Auto-updates to 9.0 should also happen just fine without hesiod
information, incidentally.)
The Athena 9.0.19 release further improved the situation for non-hesiod
updates, by using the public-linux cluster information for machines
which don't have cluster info. With this change, a 9.0 machine without
hesiod information could update to a 9.0 patch release even if 9.1 is
the current release. Unfortunately (and I just noticed this), I undid
this improvement when I moved the update script into AFS in 9.0.22, but
it should be easy to restore it now that the update script doesn't live
on workstations' local disks.