From owner-freebsd-current Tue Dec 14 19: 2:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 75A1114F62 for ; Tue, 14 Dec 1999 19:02:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA50968; Tue, 14 Dec 1999 19:02:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Eric Jones Cc: current@FreeBSD.ORG Subject: Re: sysinstall: is it really at the end of its lifecycle? In-reply-to: Your message of "Tue, 14 Dec 1999 22:01:54 EST." <385704A2.76A6E27A@colltech.com> Date: Tue, 14 Dec 1999 19:02:14 -0800 Message-ID: <50964.945226934@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My interest lies in exactly the opposite direction: I want to stick > a floppy in and have a box find an install server and follow a > pre-defined recipe for building itself, ala Jumpstart or Kickstart. And you're far from alone in wanting this, another reason I've been wanting to go to a script-based installation for some time. It's not at all difficult to imagine an installer which comes in two-part form: /stand/setup /stand/setup.tcl The latter actually containing just about *all* the user interaction and "installer behavior" that the user experiences during an installation of FreeBSD. That means that if you want to modify the installer to put "Case Western University Special Custom Installation" at the top of the first menu and add lots of distributions of purely academic (haha) interest to the appropriate submenus, it's a simple matter of mounting a floppy and editing a text file. Needless to say, this would also make translation efforts a lot easier. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message