Re: [HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports)
On Jul 2, 2012, at 6:24 PM, Devin Teske wrote: > > On Jun 30, 2012, at 3:47 PM, Bruce Cran wrote: > >> On 28/06/2012 00:11, Devin Teske wrote: >>> I'd like to announce that I intend to import bsdconfig(8) today. >> >> I haven't seen this get committed yet - was there a problem? >> > > No problems. A long weekend put the damper on the process but it has picked > up again. > > By week's end there should be more info. Just committed! See SVN r238438 http://svnweb.FreeBSD.org/base?limit_changes=0&view=revision&revision=238438 In the additional time that was taken many people were spoken with. The only thing that has really changed is that phk recommended adding a "WITH_BSDCONFIG" hook, and so that was done. Happy Day! -- 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports)
On Jun 30, 2012, at 3:47 PM, Bruce Cran wrote: > On 28/06/2012 00:11, Devin Teske wrote: >> I'd like to announce that I intend to import bsdconfig(8) today. > > I haven't seen this get committed yet - was there a problem? > No problems. A long weekend put the damper on the process but it has picked up again. By week's end there should be more info. -- 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports)
On 28/06/2012 00:11, Devin Teske wrote: I'd like to announce that I intend to import bsdconfig(8) today. I haven't seen this get committed yet - was there a problem? -- Bruce Cran ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports)
On Thu, 28 Jun 2012 07:27:19 +0200 "O. Hartmann" wrote: [skipped] > > What will happen with the old sysinstall? Well, I'm glad to read that svn log -v -r 225937 svn://svn.freebsd.org/base > 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 > -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports)
On 06/28/12 01:11, Devin Teske wrote: > Hi All, > > I'd like to announce that I intend to import bsdconfig(8) today. > > === > > Run-up… > > Q. What is bsdconfig(8)? > A. dialog(1) based post-install configuration utility for > configuring/managing various aspects of FreeBSD. > > Q. What does it look like? > A. No screenshots, but I do have a graphic illustrating the menu layout… > > http://druidbsd.sf.net/download/bsdconfig/bsdconfig-0.7.0-ic.svg > > Q. Why do we need this in base? > A. Because this functionality was exactly produced by sysinstall(8) which has > been deprecated (will not exist in FreeBSD 10). FreeBSD-9 is where bsdinstall > is being evaluated as a replacement for the install functionality of > sysinstall(8) meanwhile bsdconfig is to replace the configuration/management > functionalities of sysinstall. > > 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. > > 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. > > 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 directory to add > the new SUBDIR). > > Any other questions, don't hesitate to ask. > > === > > Heads-up… > > Code will land in src/usr.sbin/bsdconfig and _nowhere_ else. > > The code will be voluminous (~20k LOC across ~150 files including ~30 > Makefiles). > > The code is entirely in sh(1) (don't knock it until you've seen it). > > 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! > > All code was written by Ron McDowell and myself. > > === > > If there are no complaints by End-Of-Day (EOD), I'll go ahead and import. > 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 signature.asc Description: OpenPGP digital signature
[HEADS-UP] Import of src/usr.sbin/bsdconfig from sysutils/bsdconfig (ports)
Hi All, I'd like to announce that I intend to import bsdconfig(8) today. === Run-up… Q. What is bsdconfig(8)? A. dialog(1) based post-install configuration utility for configuring/managing various aspects of FreeBSD. Q. What does it look like? A. No screenshots, but I do have a graphic illustrating the menu layout… http://druidbsd.sf.net/download/bsdconfig/bsdconfig-0.7.0-ic.svg Q. Why do we need this in base? A. Because this functionality was exactly produced by sysinstall(8) which has been deprecated (will not exist in FreeBSD 10). FreeBSD-9 is where bsdinstall is being evaluated as a replacement for the install functionality of sysinstall(8) meanwhile bsdconfig is to replace the configuration/management functionalities of sysinstall. 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. 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. 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 directory to add the new SUBDIR). Any other questions, don't hesitate to ask. === Heads-up… Code will land in src/usr.sbin/bsdconfig and _nowhere_ else. The code will be voluminous (~20k LOC across ~150 files including ~30 Makefiles). The code is entirely in sh(1) (don't knock it until you've seen it). 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! All code was written by Ron McDowell and myself. === If there are no complaints by End-Of-Day (EOD), I'll go ahead and import. -- Cheers, 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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
