From owner-freebsd-current@FreeBSD.ORG Wed Nov 7 15:39:11 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D77DC16A418 for ; Wed, 7 Nov 2007 15:39:11 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 9DF2513C494 for ; Wed, 7 Nov 2007 15:39:11 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.1/8.14.1) with ESMTP id lA7FcpSD057105; Wed, 7 Nov 2007 09:38:51 -0600 (CST) (envelope-from scf@FreeBSD.org) Date: Wed, 7 Nov 2007 09:38:51 -0600 (CST) From: "Sean C. Farley" To: "Aryeh M. Friedman" In-Reply-To: <47312AA2.6000701@gmail.com> Message-ID: References: <47312AA2.6000701@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on mail.farley.org Cc: freebsd-current@FreeBSD.org Subject: Re: best way to configure a machine for kernel development X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2007 15:39:11 -0000 On Tue, 6 Nov 2007, Aryeh M. Friedman wrote: > I decided to put my fingers where my mouth is and jump into kernel > development instead of just complaining. Configuring a machine > properly to do this most effectivally I guess is the next step. I > only have one machine (I have some modest but non-critical production > stuff that needs to continue working). Some options I have come up > with: > > 1. Just hack my current sources and keep diffs (some automated way > would be nice of edit-->make diff) The Committer's Guide has information[1] on how to setup your environment to keep a local copy of CVS on your system. You will need to use a public CVSup server along with using the CVSup[2] tool, as opposed to csup, since it supports CVS mode. Begin with /usr/share/examples/cvsup/cvs-supfile for obtaining the source. After creating your local copy, you can checkout from this repository. Now, you will have a way to make diff's easily. I actually have a /usr/FreeBSD directory with multiple checkouts (HEAD, RELENG_6 and RELENG_7). This will involve you setting environment variables correctly to use a non /usr/src directory. Read build(7) for more information. Personally, I use a script[3] I wrote for building and installing. > 2. Use QEMU to create a development machine Unfortunately, device driver development will need access to the actual hardware. QEMU will only provide the guest OS its own emulated devices. > 3. Someone said something about unionfs and/or using a cvs mirror but > I missed that completely missed that > > Any other suggestions. Also since I tend to be a little slow on the > learning curve can you also point me to some good howto/tutorials on > what ever solution you suggest? Sean 1. http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/cvs.operations.html 2. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html 3. http://www.farley.org/freebsd/#fbinst -- scf@FreeBSD.org