From owner-freebsd-questions@FreeBSD.ORG Tue Dec 11 22:44:28 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3FA30163; Tue, 11 Dec 2012 22:44:28 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id EE3A68FC08; Tue, 11 Dec 2012 22:44:27 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id qBBMiRCt008956 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 11 Dec 2012 16:44:27 -0600 Received: from [10.0.0.102] (10.14.152.61) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 11 Dec 2012 16:44:26 -0600 Subject: Re: make release and mfsroot MIME-Version: 1.0 (Apple Message framework v1283) From: Devin Teske In-Reply-To: Date: Tue, 11 Dec 2012 14:44:24 -0800 Message-ID: <673FA8EA-4492-49E1-8316-95D88A45FB1D@fisglobal.com> References: <04ABE8E0-8D63-4C68-92C4-69B516818160@fisglobal.com> <1531C946-2259-4295-B388-42DC94FBE7FB@fisglobal.com> To: Rick Miller X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2012-12-11_09:2012-12-11,2012-12-11,1970-01-01 signatures=0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: 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: Tue, 11 Dec 2012 22:44:28 -0000 On Dec 11, 2012, at 2:13 PM, Rick Miller wrote: > On Tue, Dec 11, 2012 at 5:05 PM, Devin Teske = wrote: >>=20 >> Though, to resize the mfsroot, I still rely on release(7) and the above >> patches. >=20 > Here's another question, have you applied this approach to > boot_crunch.conf? I simply replaced the default boot_crunch.conf with > my own in the source tree. This is how I discovered MFSSIZE, because > the resulting boot_crunch binary was larger than the available space. >=20 I've separated the various additions to mfsroot into two categories: 1. Additions that end up in the boot_crunch binary 2. All other additions I use the release(7) process to produce a custom mfsroot with finely tuned = boot_crunch, then I use the previously-shared Makefile to put more files in= (things that are separate from the boot_crunch). You can read more about my procedure here (complete recipe for customizing = any part of the mfsroot, while spending as little time in the release(7) pr= ocess as possible): http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/free= bsd/patches/README?revision=3D1.2&view=3Dmarkup The above is for the 9.x line, for the 8.x line the instructions are *sligh= tly* different: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid83/dep/fr= eebsd/patches/README?revision=3D1.1&view=3Dmarkup You can my customizations to boot_crunch: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/free= bsd/patches/local_patches/release%3A%3Ai386%3A%3Aboot_crunch.conf.patch?rev= ision=3D1.2&view=3Dmarkup and again, slightly different for 8.x: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid83/dep/fr= eebsd/patches/local_patches/release%3A%3Ai386%3A%3Aboot_crunch.conf.patch?r= evision=3D1.1&view=3Dmarkup --=20 Devin _____________ 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.