Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Jan 2012 14:41:22 -0800
From:      Devin Teske <devin.teske@fisglobal.com>
To:        "'Warren Block'" <wblock@wonkity.com>, "'Ron McDowell'" <rcm@fuzzwad.org>
Cc:        'Lawrence Stewart' <lstewart@freebsd.org>, devin.teske@fisglobal.com, freebsd-sysinstall@freebsd.org, 'Marcel Moolenaar' <marcel@xcllnt.net>
Subject:   RE: sysinstall as a post-install tool
Message-ID:  <05fd01cccb31$fcbc80f0$f63582d0$@fisglobal.com>
In-Reply-To: <alpine.BSF.2.00.1201032036100.19921@wonkity.com>
References:  <CAF6rxgnVAbRd-mrN%2BykDmXafPzQRJgaw9q=%2Bi%2BXqTzL26gWh5Q@mail.gmail.com>	<F80CD5E2-0CC0-4872-9B25-72C4ABCC5F42@xcllnt.net>	<4F03AF24.70102@freebsd.org> <4F03BE93.9040708@fuzzwad.org>	<CAF6rxgnzLEfRr3jr1GiGC=zsmDFjwfd3r%2B_UVSEQnCudrNETgQ@mail.gmail.com>	<4F03C38D.1080909@fuzzwad.org> <alpine.BSF.2.00.1201032036100.19921@wonkity.com>

next in thread | previous in thread | raw e-mail | index | archive | help


> -----Original Message-----
> From: owner-freebsd-sysinstall@freebsd.org [mailto:owner-freebsd-
> sysinstall@freebsd.org] On Behalf Of Warren Block
> Sent: Tuesday, January 03, 2012 7:40 PM
> To: Ron McDowell
> Cc: Marcel Moolenaar; freebsd-sysinstall@freebsd.org; Lawrence Stewart
> Subject: Re: sysinstall as a post-install tool
> 
> On Tue, 3 Jan 2012, Ron McDowell wrote:
> 
> > Eitan Adler wrote:
> >> On Tue, Jan 3, 2012 at 9:50 PM, Ron McDowell <rcm@fuzzwad.org> wrote:
> >>
> >>> I [Ron] just added myself to the sysinstall list.
> >>>
> >>
> >> Good
> >>
> >>> What I envision is a text based system administration suite that
> >>> will [hopefully] do everything that the "Configure" option on the
> >>> top level of the sysinstall menu does.  I see it as being part of
> >>> the base OS, such that once one has rebooted from HD after the
> >>> install and logged in as root [or
> >>> user+su], a menu can be brought up by entering "sysadmin" or such.
> >>> user+Does
> >>> "sysadmin" work for a name?  I kinda like it.
> >>>
> >>
> >> Do you plan on this tool being run "late in the game" after the
> >> system has been used for a while or this is a "welcome new user" only tool?
> >>
> >
> > I want it to be both.  Similar in concept to scoadmin on SCO, sysadm
> > on SVR4, smit on AIX if you're familiar with any of them.
> 
> 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.
-- 
Devin

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05fd01cccb31$fcbc80f0$f63582d0$>