Re: biweekly debian-installer status report
> Hmmm... with a jumpstart floppy, a menu of standard install types
> gotten from a spot on the CD and/or tftp/ftp/http server, AND a tool
> to create those config data files? It ought to allow creation of
> several (possibly related and mostly identical) configurations. When
> it starts, you'd tell it which one this is, and the rest is auto?
if we do things right, automated installed "fall" right out of using
debconf with minimal if any extra code needed.
> The recent article in one of the Linux magazines about using netboot
> and dhcp to automate installs in a computing lab was very
> interesting. How can debian installer do something like that?
i didn't see this article, but in many cases these are done with ghost
images -- you create a boot image, and all machines either boot with
that image (nfsroot type), or you duplicate the image over to the machine.
it would seem that automated installs using either an "answer file" that
is part of your installation media, or using configuration gotten from a
central configuration database (ldap, pgsql, or what have you) will give
you the flexibility needed to do mass installs in, for example, a lab
environment.
randolph
--
Debian Developer <tausq@debian.org>
http://www.TauSq.org/
Reply to: