[3085] in SIPB_Linux_Development
Re: SIPB Installer Bugs: Custom Install
daemon@ATHENA.MIT.EDU (Alex Coventry)
Wed Oct 11 16:02:48 2000
Date: Wed, 11 Oct 2000 16:02:03 -0400
Message-Id: <200010112002.QAA08305@w20-575-38.mit.edu>
From: Alex Coventry <alex_c@MIT.EDU>
To: warlord@MIT.EDU
Cc: linux-dev@MIT.EDU
In-Reply-To: <sjm4s2j1ddf.fsf@indiana.mit.edu> (message from Derek Atkins on
11 Oct 2000 13:44:44 -0400)
> I would certainly like to be able to install the kernel sources at
> install time. I would also want to be able to install netscape, a
> compiler and development suite, java... But honestly I'm far enough
> removed that I don't know what's installed locally by default, and
> what isn't. I would like to be able to install a machine that can
> work on or off the net, but still be Athenized.
Hmm, I reckon the upgrader that comes with the standard installer would
serve in those cases.
My main concern with the custom installer is that it means there may be
more non-standard configurations out there that we're going to be
expected to help with, because they arose from our installer. Someone
who is competent enough use the custom installer is going to be able to
grab extra rpm's themselves, so the advantage of including it doesn't
seem that great to me. On the other hand I would think that providing
the custom install option to everyone greatly increases the risk that
people who don't know what they're doing end up with a broken
configuration that they expect us to help them fix. Perhaps someone
with more experience in tending to a widely used distribution would have
a better idea of how serious this risk is.
Alex.
