Date: Mon, 14 Oct 1996 11:34:58 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: chiuk@cs.indiana.edu (Kenneth Chiu) Cc: hackers@freebsd.org Subject: Re: Setting Up a Kernel Hacking Machine Message-ID: <199610140205.LAA11038@genesis.atrad.adelaide.edu.au> In-Reply-To: <199610122011.PAA18989@moose.cs.indiana.edu> from "Kenneth Chiu" at Oct 12, 96 03:11:37 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Kenneth Chiu stands accused of saying: > > I'm interested in hacking some on the kernel, maybe work on a driver. > What's the recommended way to set up a single machine for this? Install the most recent -SNAP, make sure you have plenty of space on /var for kernel crash dumps. > I'm thinking along the lines of a set of partitions for running > 2.1.5-RELEASE that I would use for development, and a single partition > with -current or maybe -SNAP that I would use for testing. As a general rule, -current is stable enough for development. If you lurk on the -current list and avoid building new kernels for a day or so after people like John make major changes, it's actually very good. > So I would build from the 2.1.5 system into the -current partition, and > then reboot to the -current partition to test. Does this sound > workable? It could be done, but it would be a lot of (wasted IMHO) effort. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610140205.LAA11038>