sysinstall as a post-install tool

[Warren Block]

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.