Date: Tue, 25 Jul 2006 11:13:01 -0500 From: Eric Anderson <anderson@centtech.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-fs@freebsd.org Subject: Re: Advice for hacking on ufs/ffs Message-ID: <44C6430D.1050506@centtech.com> In-Reply-To: <86wta1en0e.fsf@xps.des.no> References: <20060724185205.17021.qmail@web31812.mail.mud.yahoo.com> <86wta1en0e.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/25/06 10:13, Dag-Erling Smørgrav wrote: > 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 DES - anything special with the nfs root'ed box, to make this work well? The only reason I didn't set this up for my work is because it isn't portable.. :) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44C6430D.1050506>