Date: Tue, 25 Jul 2006 17:13:05 +0200 From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Shane Adams <adamsch1@yahoo.com> Cc: freebsd-fs@freebsd.org Subject: Re: Advice for hacking on ufs/ffs Message-ID: <86wta1en0e.fsf@xps.des.no> In-Reply-To: <20060724185205.17021.qmail@web31812.mail.mud.yahoo.com> (Shane Adams's message of "Mon, 24 Jul 2006 11:52:05 -0700 (PDT)") References: <20060724185205.17021.qmail@web31812.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Shane Adams <adamsch1@yahoo.com> writes: > I'm a programmer that is new to kernel development. I'm interested > in hacking around on UFS and FFS. I only have one machine so I > copied the complete sys/ufs code to a new directory under fs, and > changed a few things to get it to compile and mount. Everything > works, and I was ready to start hacking without worrying so much > about screwing up my system. > > Naturally I've rebooted the machine a few times since then, and I > was wondering if anyone has advice for a fledgling kernel > programmer. (Best practices) Get a test machine with a PXE-capable network adapter, and set up your workstation as bootp / dhcp and NFS server. Having a dedicated test box will save time as you won't have to reboot your workstation to test your code, and setting it up diskless will help even further. A serial console cable will help even more, as it will save you from moving from one keyboard to another and will give you a scrollback of the test machine's console from which you can copy / paste error messages, backtraces etc. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wta1en0e.fsf>