Date: Thu, 28 Jun 2012 07:27:19 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Devin Teske <dteske@freebsd.org> Cc: freebsd-current@freebsd.org, Ron McDowell <rcm@fuzzwad.org>, Devin Teske <devin.teske@fisglobal.com> Subject: Re: [HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports) Message-ID: <4FEBEB37.5060502@zedat.fu-berlin.de> In-Reply-To: <AAD01C0C-04F6-46ED-8D2C-F2F36842C24C@fisglobal.com> References: <AAD01C0C-04F6-46ED-8D2C-F2F36842C24C@fisglobal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA05B439FD961D78A58367EF4 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 06/28/12 01:11, Devin Teske wrote: > Hi All, >=20 > I'd like to announce that I intend to import bsdconfig(8) today. >=20 > =3D=3D=3D >=20 > Run-up=85 >=20 > Q. What is bsdconfig(8)? > A. dialog(1) based post-install configuration utility for configuring/m= anaging various aspects of FreeBSD. >=20 > Q. What does it look like? > A. No screenshots, but I do have a graphic illustrating the menu layout= =85 >=20 > http://druidbsd.sf.net/download/bsdconfig/bsdconfig-0.7.0-ic.svg >=20 > Q. Why do we need this in base? > A. Because this functionality was exactly produced by sysinstall(8) whi= ch has been deprecated (will not exist in FreeBSD 10). FreeBSD-9 is where= bsdinstall is being evaluated as a replacement for the install functiona= lity of sysinstall(8) meanwhile bsdconfig is to replace the configuration= /management functionalities of sysinstall. >=20 > Q. Did you discuss this with anyone? > A. Everyone that would listen in the past 6 months as we run up to the = 9.1 code freeze. >=20 > Q. Did anyone test this? > A. Ron, myself, and about 8 others in the community did both high-level= testing, low-level review, and more over the past 6 months. >=20 > Q. If it doesn't go well, can we back it out? > A. Sure -- it's entirely self contained. src/usr.sbin/bsdconfig is the = only directory being touched (oh, and the Makefile in the parent director= y to add the new SUBDIR). >=20 > Any other questions, don't hesitate to ask. >=20 > =3D=3D=3D >=20 > Heads-up=85 >=20 > Code will land in src/usr.sbin/bsdconfig and _nowhere_ else. >=20 > The code will be voluminous (~20k LOC across ~150 files including ~30 M= akefiles). >=20 > The code is entirely in sh(1) (don't knock it until you've seen it). >=20 > The code used in this tool and all sub-modules was developed primarily = over a 150-day period, but in reality contains code developed and revised= over the past 5 years, entirely BSD licensed! >=20 > All code was written by Ron McDowell and myself. >=20 > =3D=3D=3D >=20 > If there are no complaints by End-Of-Day (EOD), I'll go ahead and impor= t. >=20 What will happen with the old sysinstall? Well, I'm glad to read that FreeBSD makes a step forward, but maybe there are some people who want to be stick with the old sysinstall. While bsdconfig is flushed in from ports, sysinstall could be flushed out into the ports? If the question or suggestion sounds not rational, dump it ... Regards Oliver --------------enigA05B439FD961D78A58367EF4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJP6+s+AAoJEOgBcD7A/5N8r8kIANfc5VevJalYbCRz6SEAGL5R +L/yL8bH5G8z3cJhZOoMN3+wIjEUAxWYPdP0QK1vB9FBqhVTsFKNASFIXGbzKmCt JUvi5SzDwOH9ruWWXJaHw2vK/LoruwUuxYMeDWS/kd3YWJgcDRIHzPvChRT7c1No 3NU+CMqUx0xnz/OwI2GaXVFEvuYI80mEVH5FYrnRQOavmcFmScbIsaufPBd13wJK LAO3rpPA3B7TlSk3wzuhP0cvE9qKsj09SNJchRKGzC1tPONRlFi8ImymN/cySnKC /ZSbBT19OrFNOhJYtMXkUHpi8lt43tkWm/dO4poX78D6aFlqV9vucQFvEMNT2pM= =9/OM -----END PGP SIGNATURE----- --------------enigA05B439FD961D78A58367EF4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FEBEB37.5060502>