From owner-freebsd-questions@FreeBSD.ORG Thu Aug 1 18:20:38 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 30D81535; Thu, 1 Aug 2013 18:20:38 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E9B5D22B5; Thu, 1 Aug 2013 18:20:37 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa03.fnfis.com (8.14.5/8.14.5) with ESMTP id r71IKaV6022591 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 1 Aug 2013 13:20:36 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Thu, 1 Aug 2013 13:20:35 -0500 From: "Teske, Devin" To: Amitabh Kant Subject: Re: Make Release Thread-Topic: Make Release Thread-Index: AQHOjtJECsxKvcvx/UeR7ZtcfRlfPpmA4r6AgAADpwCAABEggIAABkgA Date: Thu, 1 Aug 2013 18:20:35 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201FFEFDE@ltcfiswmsgmb21> References: <13CA24D6AB415D428143D44749F57D7201FFEB17@ltcfiswmsgmb21> <13CA24D6AB415D428143D44749F57D7201FFEEA3@ltcfiswmsgmb21> In-Reply-To: <13CA24D6AB415D428143D44749F57D7201FFEEA3@ltcfiswmsgmb21> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-08-01_08:2013-08-01,2013-08-01,1970-01-01 signatures=0 Cc: "Sam Fourman Jr." , Devin Teske , FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 18:20:38 -0000 On Aug 1, 2013, at 10:58 AM, Teske, Devin wrote: >=20 > On Aug 1, 2013, at 9:56 AM, Amitabh Kant wrote: >=20 >> On Thu, Aug 1, 2013 at 10:13 PM, Teske, Devin wrote: >> I'm hoping that my very open development documentation on customizing th= e release(7) process for producing DruidBSD releases can help you out here. >>=20 >> I've documented much of the internals of the release(7) process (albeit,= relevant to the RELENG_8 release(7) Makefile; in RELENG_9 it's still relev= ant to /usr/src/release/Makefile.sysinstall ... but I gather that much of t= he knobs may still exist in HEAD). >>=20 >> Have a read through this revision-controlled text file... >>=20 >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/druidbsd/druid/dep/freebsd/pa= tches/README?revision=3D1.2&view=3Dmarkup >>=20 >> ALSO NOTE: Yes, the file is dated... it talks about cvsup instead of svn= . My hope is that the doco can be a good starting point (even if the data i= s a bit dated). >>=20 >> In there, you'll find things like (relevant to RELENG_9): >>=20 >> make -f Makefile.sysinstall release \ >> MAKE=3D"/usr/bin/env CFLAGS=3D-DDRUID make" \ >> CHROOTDIR=3D/usr/release EXTSRCDIR=3D/usr/src KERNELS_BAS= E=3D \ >> NODOC=3DYES NO_FLOPPIES=3DYES NOCDROM=3DYES NOPORTS=3DYES= \ >> WORLD_FLAGS=3D-DWITHOUT_OPENSSL PATCH_FLAGS=3D-N \ >> LOCAL_PATCHES=3D/tmp/druid.patches \ >> LOCAL_SCRIPT=3D/tmp/local_script.sh |& tee release.log >>=20 >> Take special note of the "LOCAL_SCRIPT=3D" option. >>=20 >> Maybe, just maybe, the bsdinstall-specific release(7) process supports L= OCAL_SCRIPT too. If it doesn't... why not? >> -- >> Devin >>=20 >> Devin >>=20 >> Do you have any idea if there have an changes to bsdinstall process (on = scripting side) in the upcoming 9.2 ?=20 >>=20 >=20 > [snip] > Beyond that... ( ok that's enough for this e-mail ). More includes (for the advanced scripting -- again, tapping into what /usr/= share/bsdconfig/script.subr provides), there are sub-directories in /usr/sh= are/bsdconfig (but again, script.subr brings them all in): media/ -- one file for each type of media (FTP, HTTP, HTTP Proxy, NFS, ... = etc.) networking/ -- scripts for getting, setting, and interactively modifying ne= twork packages/ -- package management password/ -- root password startup/ -- rc.conf(5) and startup services timezone/ -- like tzsetup usermgmt/ -- user management stuff Each of those includes a lot of low-level functionality but it's all docume= nted very well. That being said... there's one more avenue of scripting. All of the bsdconfig(8) modules that act as front-ends to the above librari= es. Those are in /usr/libexec/bsdconfig -- and you can call those from your bsd= install ``/etc/installerconf'' too. # Example A /usr/libexec/bsdconfig/090.timezone/timezone However, it's far easier to just say: # Example B bsdconfig timezone For a list of keywords to the modules, say either: bsdconfig -h *or* Peruse the diagram (which is generated by "bsdconfig dot"): http://druidbsd.sourceforge.net/download/bsdconfig/bsdconfig-HEAD-20130506-= 3i.svg The green parallelograms are the bsdconfig keywords, and the blue rectangle= s represent the modules (mousing over it will show the /usr/libexec/bsdconf= ig path in a tooltip). --=20 Devin > --=20 > Devin >=20 > _____________ > The information contained in this message is proprietary and/or confident= ial. 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 awa= re that any message addressed to our domain is subject to archiving and rev= iew by persons other than the intended recipient. Thank you. _____________ 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.