From owner-freebsd-stable@FreeBSD.ORG Tue Jan 18 17:27:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3C8E16A524 for ; Tue, 18 Jan 2005 17:27:03 +0000 (GMT) Received: from ares.wolfpond.org (ns1.wolfpond.org [62.212.96.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FC5643D64 for ; Tue, 18 Jan 2005 17:26:58 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (aoi.wolfpond.org [IPv6:2001:7a8:24db:1:20c:76ff:feb4:27e1]) by ares.wolfpond.org (8.13.1/8.13.1) with ESMTP id j0IHQuPV029686; Tue, 18 Jan 2005 18:26:56 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.1/8.13.1) with ESMTP id j0IHR5sU054859; Tue, 18 Jan 2005 18:27:05 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.1/8.13.1/Submit) id j0IHR5xX054858; Tue, 18 Jan 2005 18:27:05 +0100 (CET) (envelope-from ftigeot) Date: Tue, 18 Jan 2005 18:27:05 +0100 From: Francois Tigeot To: David Landgren Message-ID: <20050118172705.GB54509@aoi.wolfpond.org> References: <41ED440C.9090401@landgren.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41ED440C.9090401@landgren.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: Building your own FreeBSD installation CD-ROM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 17:27:07 -0000 On Tue, Jan 18, 2005 at 06:14:52PM +0100, David Landgren wrote: > > how does one go about creating a FreeBSD install CD-ROM? I'd like to be > able to build my own CD-ROM with as much as possible of the install > process done automatically. For instance, what parts of FreeBSD to > install: X or not, games or not, etc. etc. And which ports to install > straight away. I could also set up cfengine so that as soon as the > machine came to life it could go and connect to my cfengine repository > and download all the latest configurations to move into operational status. There is some documentation in /usr/src/release on how to build a custom release (I did it successfully around 4.4 time). It is also possible to script the installer via a configuration file. Look at sysinstall(8) manpage for details. -- Francois Tigeot