From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 9 00:06:19 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 D944312E for ; Fri, 9 Nov 2012 00:06:19 +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 928248FC0A for ; Fri, 9 Nov 2012 00:06:19 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa03.fnfis.com (8.14.5/8.14.5) with ESMTP id qA906Ito020062 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 8 Nov 2012 18:06:18 -0600 Received: from [10.0.0.101] (10.14.152.61) by smtp.fisglobal.com (10.132.206.17) with Microsoft SMTP Server (TLS) id 14.2.309.2; Thu, 8 Nov 2012 18:06:17 -0600 Subject: Re: Custom FreeBSD usb memstick MIME-Version: 1.0 (Apple Message framework v1283) From: Devin Teske In-Reply-To: <509C4213.3090106@fisglobal.com> Date: Thu, 8 Nov 2012 16:06:16 -0800 Message-ID: <4DE05C40-9AAB-4680-AB5F-D67C29BE7778@fisglobal.com> References: <509C2E17.9000406@fisglobal.com> <509C4213.3090106@fisglobal.com> To: "Sam Fourman Jr." 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.8185, 1.0.431, 0.0.0000 definitions=2012-11-08_10:2012-11-08,2012-11-08,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: FreeBSD Hackers , Dave Robison X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 00:06:20 -0000 Slowly working my way to HEAD. 9.0-R is the latest I've done (and still wai= ting patiently for 9.1-R). Druid is unique in that you can create a custom USB memstick that also can = be burned to CD or DVD (with zero modifications). When getting started, keep in mind that you can do these steps on Mac OS X,= Linux, Cygwin, and (uh) FreeBSD :) 1. Find/Browse the code here=85 http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druidbsd/ 2. Get the code=85 In Tarball form (22.6MB): http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druidbsd/?view= =3Dtar or Instructions on how to download with CVS: http://sourceforge.net/projects/druidbsd/develop NOTE: When logging in anonymously, simply press ENTER when prompted for a p= assword NOTE: Use a modulename of druidbsd/druidbsd when checking out the code NOTE: Downloaded module measures about 30MB in size 3. Execute the following: cd druidbsd ./configure NOTE: If you went the CVS route, the first command is instead: cd druidbsd/= druidbsd 4. Dependency checks: In the output of "configure" from step 3 above (which is rather small), mak= e sure no commands have been mapped "/bin/false" (except for "false" itself= , naturally). Basically, you'll need GNU make, mkisofs, and a few basic shell utilities. 5. [Optional] Customize: If you want to customize the kernel that is used, it's in "mdroot/kernels/" NOTE: If you change the name of the kernel, edit the file "mdroot/boot/menu= .rc" (kernel paths are at the top) NOTE: You can load multiple kernels if you want (and configure the menu to = display them for selection) If you want to customize the boot menu, that's in "mdroot/boot/menu.rc" If you want to add kernel modules, those go into "mdroot/boot/modules/" If you want to customize the mfsroot, there's a whole framework for that in= "dep/freebsd/mfsroot/" (however, you'll need a FreeBSD host to customize t= hat portion). If you want to simply add new commands to DruidBSD, dump new binaries into = "src/freebsd/rescue/" NOTE: There's a corresponding "src/freebsd/rescue/lib/" for you to dump lib= rary dependencies. If you want to add other miscellaneous files, just dump them into "src/free= bsd/". 6. Produce an ISO for mastering to USB stick: make NOTE: Sorry, this has to be GNU make (so on FreeBSD, say "gmake" instead). NOTE: This produces the ISO file (image) of your custom FreeBSD memstick 7. Play Use the instructions here to get your ISO onto physical media: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/tool= s/ NOTE: Start with "README" NOTE: There are many methods for many operating systems documented and even= some tools for download (such as a Win32 GUI tool for imaging the ISO onto= USB stick). Remember, that ISO can be burned to optical media _and_ imaged to USB stick= (or any hard disk for that matter) without changing anything about the ISO= (that's the nature of the DRUID architecture). I demonstrated much of this at the last DevSummit, but it's not part of Fre= eBSD. If you have any questions, let me know. --=20 Devin On Nov 8, 2012, at 3:36 PM, Robison, Dave wrote: > Druid is Devin's baby so I will CC him >=20 > I do not think he has done HEAD on druid yet... but it's not a bad idea. >=20 >=20 > Dave >=20 >=20 > On 11/08/2012 15:35, Sam Fourman Jr. wrote: >> On Thu, Nov 8, 2012 at 4:11 PM, Robison, Dave >> wrote: >>> If you're just looking for a release on memstick, check out druidbsd >>>=20 >>> http://druidbsd.sourceforge.net/ >>>=20 >>> If you're doing it to learn the process, I'm sure you can learn a few >>> things from druidbsd anyway... >>>=20 >>> Enjoy >>>=20 >>> Dave >>=20 >> Thank you Dave, >>=20 >> do you build a version of DruidBSD based on HEAD? >>=20 >> im really trying to learn the process, and id like to know how to >> alter the install image size.. then ill start with customization from >> there. >>=20 >=20 >=20 > --=20 > Dave Robison > Sales Solution Architect II > FIS Banking Solutions > 510/621-2089 (w) > 530/518-5194 (c) > 510/621-2020 (f) > daver@vicor.com > david.robison@fisglobal.com _____________ 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.