[6237] in Release_7.7_team
Re: publicity
daemon@ATHENA.MIT.EDU (Tim Abbott)
Thu Feb 26 23:50:17 2009
Date: Thu, 26 Feb 2009 23:49:39 -0500 (EST)
From: Tim Abbott <tabbott@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
cc: Evan Broder <broder@mit.edu>, William Cattey <wdc@mit.edu>,
release-team@mit.edu, debathena-dev@mit.edu
In-Reply-To: <46E6EB35-FDDA-4486-B8C1-C3AB215D4270@mit.edu>
Message-ID: <alpine.DEB.2.00.0902262346070.1724@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Flag: NO
X-Spam-Score: 0.00
On Thu, 26 Feb 2009, Jonathan Reed wrote:
> > (1) a merged installer is committed and deployed on debathena.mit.edu
>
> It looks like the major differences are:
>
> 1) The Debathena installer asks you guided questions to figure out whether you
> want standard, login, or workstation, whereas the Athena 10 installer makes
> you pick one by name
Yeah, the Athena 10 version here is just plain better.
> 2) The Debathena installer will install module-assistant and build openafs for
> you if it's not available for your kernel
> 3) The Athena 10 installer can deal with unattended cluster installs, and asks
> about thirdparty and stuff.
>
> Obviously #3 needs to happen.
Right.
> For #1, I would say that the script should present the available options, and
> make you pick one by name. At the bottom, it can say something like "For more
> information on selecting the installation option that best suits you, see
> http://debathena.mit.edu/beta/installation-options" (I'll keep that URL the
> same).
Sounds good.
> For #2, I have no objection to it building openafs if modules aren't
> available, assuming there are no major problems with this. If the build fails
> for some reason, it should explicitly tell the user that something really bad
> happened and they should probably e-mail debathena@ before trying to use their
> machine.
Sounds good.
As I mentioned previously, I will try to ensure that this happens on
Saturday if it isn't done before then.
-Tim Abbott
