Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Jan 2012 20:07:59 -0800
From:      Devin Teske <devin.teske@fisglobal.com>
To:        Eitan Adler <lists@eitanadler.com>
Cc:        Devin, Garrett Cooper <yanegomi@gmail.com>, Marcel Moolenaar <marcel@xcllnt.net>, Lawrence Stewart <lstewart@freebsd.org>, freebsd-sysinstall@freebsd.org
Subject:   Re: sysinstall as a post-install tool
Message-ID:  <AE439876-396E-4F5D-AD28-142A500E2E46@fisglobal.com>
In-Reply-To: <CAF6rxgkxUR0fOaPEKFKOF9LDJD64BOLxdehPOPrm0NiY__H5Gw@mail.gmail.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> <964E978A-C016-4A53-A034-8959140CDF68@fisglobal.com> <CAF6rxgkxUR0fOaPEKFKOF9LDJD64BOLxdehPOPrm0NiY__H5Gw@mail.gmail.com>

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

On Jan 3, 2012, at 7:30 PM, Eitan Adler wrote:

> On Tue, Jan 3, 2012 at 10:14 PM, Devin Teske <devin.teske@fisglobal.com> =
wrote:
>> host-setup actually leverages the power and safety of my sysrc(8) utility
>> (just added to ports tree as sysutils/sysrc).
>>=20
>> In fact, sysrc was written as a test-script solely to feed back into
>> host-setup so that we could replace sysinstall's Configure menu. We're j=
ust
>> not there with all the menu items (but we've got the most important ones=
 --
>> IMHO -- and made them rock-stable).
>=20
> I want to see these tools in the base system.

I should mention one more tool that plays into all this... tzdialog.

Part of the puzzle to completing our quest of "replacing sysinstall" involv=
ed rewriting tzsetup(8). Largely because we had written host-setup(1) to wo=
rk with Xdialog(1) and therefore thought that it would be better to have a =
tzsetup(8) that also supported Xdialog(1) rather than launching it within a=
n xterm(1) (which was not-so-nice, but does work).

In rewriting tzsetup(8) to produce tzdialog(1), I strived _very_ hard to ac=
tually make it so that you can literally line up the C-code with the sh(1)-=
code. Picking out comments that are word-for-word the same is one thing, bu=
t re-using variable names and even going as far as to invent struct-analogs=
 with the same names is another story. All the sh(1)-code follows the exact=
 same logic as the C-code. When the C-code opens the ISO-3166 table from NI=
ST and parses-out the data it needs, so does the sh(1)-code. Line-for-line,=
 we try to mimic the C-code for the express purpose that we can perhaps rep=
lace tzsetup(8), but I'll let you be the judge.

I mention all this, because host-setup(1) will automatically pick-up on the=
 existence of tzdialog(8) and prefer it as a drop-in replacement for tzsetu=
p(8), should tzdialog(8) be installed and available. Thus, achieving the ab=
ility to actually set the time-zone via host-setup from a menu-item configu=
red in a window manager or display manager (HINT: We've got our fvwm2 confi=
guration configured with "exec host-setup -sX" which correctly hands-off th=
e "-X" flag to tzdialog).

I haven't yet tossed the idea out there yet for creating a port for tzdialo=
g(8) -- this is the first that I'm suggesting -- but since I'm going to mak=
e a request to submit host-setup(8), I'd figure I ought to make a request f=
or tzdialog too, since the former can take advantage of the latter if/when =
installed.
--=20
Devin

Links:
http://druidbsd.sourceforge.net/
http://druidbsd.sourceforge.net/download/tzdialog.txt

_____________
The information contained in this message is proprietary and/or confidentia=
l. If you are not the intended recipient, please: (i) delete the message an=
d all copies; (ii) do not disclose, distribute or use the message in any ma=
nner; and (iii) notify the sender immediately. In addition, please be aware=
 that any message addressed to our domain is subject to archiving and revie=
w 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?AE439876-396E-4F5D-AD28-142A500E2E46>