Date: Sun, 3 Dec 2006 08:23:24 -0800 From: "Kevin Sanders" <newroswell@gmail.com> To: "Robert Watson" <rwatson@freebsd.org> Cc: freebsd-hackers@freebsd.org, Garrett Cooper <youshi10@u.washington.edu> Subject: Re: Tools for FreeBSD development Message-ID: <375baf50612030823p189d30f8j88507c058ce03e1f@mail.gmail.com> In-Reply-To: <20061203101352.K40536@fledge.watson.org> References: <eb7c8e2e0612021224x13598151ya58e471c9dfaa3b4@mail.gmail.com> <eb7c8e2e0612021528h47239e5cl3cf0c1e08e399329@mail.gmail.com> <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> <20061203064956.GB2405@kobe.laptop> <45728A19.7050300@u.washington.edu> <20061203101352.K40536@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/3/06, Robert Watson <rwatson@freebsd.org> wrote: > If using FreeBSD on i386/amd64 boxes, use PXE. There are quite a few "instant > setup" web pages out there that tell you how to get it running. pxeboot makes > life incredibly easy, as you can load kernels, modules, configurations, etc, > over NFS. > > Robert N M Watson > Computer Laboratory > University of Cambridge Thanks for th tips everyone. My shop has all the VMware tools, and I've used QEMU, but I prefer to develop on a real box and debug over a serial port on a second box. I'll give pxeboot a shot tomorrow. While we're on this topic, what is the best way to debug kernel modules. I would like the ability to kldload my kernel module, set a couple break points and single step through a section of code (at least). I've read Greg Lehey's http://www.lemis.com/papers/Taiwan/tutorial.pdf but it seems a little out of date. From what I gather, the situation with the kernel debugger has changed since he wrote it. Kevin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?375baf50612030823p189d30f8j88507c058ce03e1f>