From owner-freebsd-current Sun Feb 27 15:53:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 5F21E37B532 for ; Sun, 27 Feb 2000 15:53:38 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id WAA42307; Sun, 27 Feb 2000 22:30:46 GMT (envelope-from nik) Date: Sun, 27 Feb 2000 22:30:45 +0000 From: Nik Clayton To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Streamlining FreeBSD installations across many machines Message-ID: <20000227223045.A41888@catkin.nothing-going-on.org> References: <4.2.2.20000225102306.00c59600@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <4.2.2.20000225102306.00c59600@216.67.12.69>; from Forrest Aldrich on Fri, Feb 25, 2000 at 10:23:37AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 25, 2000 at 10:23:37AM -0500, Forrest Aldrich wrote: > I'm wondering if there might not be a way to streamline this install > process, such that a boot floopy and script could be created to take a > minimum amount of information, and then "do the right thing" as for the > install. Things like putting in the packet filters, the kernel, IP > config, etc. See sysinstall(8); you can script sysinstall. See src/release/sysinstall/install.cfg for an example. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message