From owner-freebsd-sysinstall@FreeBSD.ORG Thu Jan 5 01:28:52 2012 Return-Path: Delivered-To: freebsd-sysinstall@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96909106566C; Thu, 5 Jan 2012 01:28:52 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 4E74D8FC08; Thu, 5 Jan 2012 01:28:52 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q051SnBI032111; Wed, 4 Jan 2012 18:28:49 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q051Sn3c032108; Wed, 4 Jan 2012 18:28:49 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 4 Jan 2012 18:28:49 -0700 (MST) From: Warren Block To: Devin Teske In-Reply-To: <05fd01cccb31$fcbc80f0$f63582d0$@fisglobal.com> Message-ID: References: <4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org> <4F03C38D.1080909@fuzzwad.org> <05fd01cccb31$fcbc80f0$f63582d0$@fisglobal.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 04 Jan 2012 18:28:49 -0700 (MST) Cc: 'Lawrence Stewart' , freebsd-sysinstall@freebsd.org, 'Marcel Moolenaar' Subject: RE: sysinstall as a post-install tool X-BeenThere: freebsd-sysinstall@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Sysinstall Work List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2012 01:28:52 -0000 On Wed, 4 Jan 2012, Devin Teske wrote: >> bsdinstall already does some of these config things in the last menu. >> It really ought to be split into two pieces, bsdinstall to do the >> installing, and "bsdconfig", to do the configuring. bsdconfig would >> just be the pieces that are already there, run by bsdinstall after >> the installation but also useful separately. >> >> And then bsdconfig could have all the added config functionality that everyone >> loves about sysinstall. > > Dare I say what perhaps others (including myself) are thinking... > > mv host-setup bsdconfig > > I'm thinking: > > a. Take host-setup into the ports tree. > b. Shake it out. > c. Copy it into the base as "bsdconfig" > d. Start sanitizing it (remove support for legacy FreeBSD versions, etc.) > e. Start enhancing it gradually over time > f. Allow host-setup to remain in the ports tree (will retain support for legacy > FreeBSD versions, etc.) > g. I will sync-up with bsdconfig from time-to-time as bsdconfig should sync-up > with me from time-to-time. Works for me. Obviously there's a concern with duplicating effort already in bsdinstall and pc-sysinstall, and trying to have some semblance of user interface consistency. But one working system config utility is better than none, and two would be an embarrassment of riches.