From owner-freebsd-questions@FreeBSD.ORG Tue Dec 11 22:05:12 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 5D09113A; Tue, 11 Dec 2012 22:05:12 +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 17E2A8FC08; Tue, 11 Dec 2012 22:05:10 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id qBBM5AJh028454 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 11 Dec 2012 16:05:10 -0600 Received: from [10.0.0.102] (10.14.152.61) by smtp.fisglobal.com (10.132.206.16) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 11 Dec 2012 16:05:08 -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:05:04 -0800 Message-ID: <1531C946-2259-4295-B388-42DC94FBE7FB@fisglobal.com> References: <04ABE8E0-8D63-4C68-92C4-69B516818160@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_08:2012-12-11,2012-12-11,1970-01-01 signatures=0 Content-Type: text/plain; charset="windows-1252" 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:05:12 -0000 On Dec 11, 2012, at 1:50 PM, Rick Miller wrote: > Hi Devin, >=20 > On Tue, Dec 11, 2012 at 4:22 PM, Devin Teske = wrote: >> Hi Rick, >>=20 >> If you want, you could follow my approach which is to take the completed >> mfsroot.gz and use a Makefile to manage the creation of custom mfsroots >> (keeping the original unmodified, making it simpler to test different >> iterations). >=20 > Very interesting approach. I like it and will test it. >=20 > It looks as though I would need to add code to the Makefile if files > copied in later are greater in size than the space available. Would > you agree? Oh=85 forgot to mention=85 The Makefile doesn't adjust the mfsroot's size. What I do to solve that problem is patch the release(7) process to make a b= igger mfsroot (and thusly has room for more "stuff") -- this allows me to k= eep the customizations of "what goes in" at a higher level (separate from r= elease(7)) while not having to write a lot of code for resizing the mfsroot. NOTE: I've actually run into major problems with resizing an mfsroot -- tru= st me, it's safer to stick with bumping the sectors in the release(7) makef= ile. If you're working in the 8.x line, take a look at this patch for bumping th= e mfsroot size: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid83/dep/fr= eebsd/patches/world_patches/release%3A%3AMakefile.patch?revision=3D1.1&view= =3Dmarkup Meanwhile, for the 9.x line: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/dep/free= bsd/patches/world_patches/release%3A%3AMakefile.sysinstall.patch?revision= =3D1.1&view=3Dmarkup NOTE: For your purposes, you'll only need the first hunk (the second hunk i= s needed for other reasons -- reasons that are documented in the "README" o= ne-level-up in the "patches" directory from the above links). >=20 >> The advantage is that you don't have to re-perform the release(7) process >> each time you want to make a change to your mfsroot. >=20 > This is a very compelling advantage. >=20 Though, to resize the mfsroot, I still rely on release(7) and the above pat= ches. I've personally never had a need to go beyond 6000 sectors, but I know the = guys at Yahoo have gone much further. --=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.