From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 15 19:55:26 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E090D106566B for ; Wed, 15 Aug 2012 19:55:25 +0000 (UTC) (envelope-from PMahan@adaranet.com) Received: from barracuda.adaranet.com (smtp.adaranet.com [72.5.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id B28AC8FC0A for ; Wed, 15 Aug 2012 19:55:25 +0000 (UTC) X-ASG-Debug-ID: 1345059745-027ef7093817140001-P5m3U7 Received: from SJ-EXCH-1.adaranet.com ([10.10.1.29]) by barracuda.adaranet.com with ESMTP id XGbpKOXOH5ZyW8iy for ; Wed, 15 Aug 2012 12:42:25 -0700 (PDT) X-Barracuda-Envelope-From: PMahan@adaranet.com Received: from SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523]) by SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523%14]) with mapi; Wed, 15 Aug 2012 12:42:25 -0700 From: Patrick Mahan X-Barracuda-Apparent-Source-IP: fe80::7042:d8c2:5973:c523 To: "freebsd-hackers@freebsd.org" Date: Wed, 15 Aug 2012 12:42:19 -0700 Thread-Topic: Help with building private .iso media X-ASG-Orig-Subj: Help with building private .iso media Thread-Index: Ac17HhTSwXt6I2ViRQqdpt4jL67+Cg== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-cr-puzzleid: {BA3FBD50-6B83-4900-99D3-E2C0809C930C} x-cr-hashedpuzzle: FpY= UMg= AE4P CRA5 CT4m DoLs E4V3 FALq FBVI FNsH FqMQ FuJO HJi3 HNnY HrVB JOlH; 1; ZgByAGUAZQBiAHMAZAAtAGgAYQBjAGsAZQByAHMAQABmAHIAZQBlAGIAcwBkAC4AbwByAGcA; Sosha1_v1; 7; {BA3FBD50-6B83-4900-99D3-E2C0809C930C}; cABtAGEAaABhAG4AQABhAGQAYQByAGEAbgBlAHQALgBjAG8AbQA=; Wed, 15 Aug 2012 19:42:19 GMT; SABlAGwAcAAgAHcAaQB0AGgAIABiAHUAaQBsAGQAaQBuAGcAIABwAHIAaQB2AGEAdABlACAALgBpAHMAbwAgAG0AZQBkAGkAYQA= acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: UNKNOWN[10.10.1.29] X-Barracuda-Start-Time: 1345059745 X-Barracuda-URL: http://172.16.10.203:8000/cgi-mod/mark.cgi Received-SPF: none (adaranet.com: pmahan@adaranet.com does not designate permitted sender hosts) X-Virus-Scanned: by bsmtpd at adaranet.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.97753 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Cc: KERN-DEV Subject: Help with building private .iso media X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2012 19:55:26 -0000 All, Asking this here as I don't see a mailing list specifically devoted to buil= d/release issues and because I think it is a little beyond the standard -question gen= re. Our product here is based on FreeBSD (currently FreeBSD 9/STABLE) and it ha= s reached the stage where we need to create our own .iso/memstick media to handle ins= tallation of our appliances. So yesterday, after perusing release(7), I cranked up /usr/src/release/gene= rate-release.sh and capture the output to see how it was done. And I was successful in get= ting the .iso, memstick and FTP site created. So taking what I learned yesterday, I tried to apply it to our copy of the = FreeBSD source tree. Please note that we use the provided FreeBSD makefiles to build ever= ything we just make heavy use of MAKEOBJDIRPREFIX/OBJTREE/etc environment variables to con= trol where every- thing goes. So today, I tried to build the world package by doing the following at the = top of our FreeBSD source tree (after doing a buildworld) - cd /usr/home/pmahan/work/pm_ipr/ipr/src export MAKEOBJDIRPREFIX=3D/usr/home/pmahan/work/pm_ipr/ipr/amd64/obj sudo -E make TARGET_ARCH=3Damd64 TARGET=3Damd64 distrubteworld DIST=3D/us= r/home/pmahan/work/pm_ipr/ipr/amd64/dist It failed with the following: find //usr/home/pmahan/work/pm_ipr/ipr/amd64/dist/doc -empty -delete find: -delete: //usr/home/pmahan/work/pm_ipr/ipr/amd64/dist/doc: relative p= ath potentially not safe But when I check the logs for yesterday's successful run, I see - find //usr/obj/usr/src/release/dist/doc -empty -delete find //usr/obj/usr/src/release/dist/games -empty -delete find //usr/obj/usr/src/release/dist/lib32 -empty -delete sh /usr/src/release/scripts/mm-mtree.sh -m /usr/src/release/.. -F "TARGET_= ARCH=3Damd64 TARGET=3Damd64" -D "/usr/obj/usr/src/release/dist/base" I read find(1) description about '-delete' and did a quick test that seemed= to prove out that attempting to delete a fully qualified path seems to be a no-no. But = I don't understand why it did not fail yesterday. I suspect it is pilot error, but I am at a = loss to explain why. Any help, steers, slap downs appreciated Thanks, Patrick ---------------------------------------------------- Patrick Mahan Lead Technical Kernel Engineer Adara Networks Disclaimer: The opinions expressed here are solely the responsibility of th= e author and are not to be construed as an official opinion of Adara Networks.