atom feed17 messages in org.freebsd.freebsd-fsAdvice for hacking on ufs/ffs
FromSent OnAttachments
Shane AdamsJul 24, 2006 6:51 pm 
Eric AndersonJul 24, 2006 7:06 pm 
Shane AdamsJul 24, 2006 7:11 pm 
Shane AdamsJul 24, 2006 7:41 pm 
Eric AndersonJul 24, 2006 7:50 pm 
Dag-Erling SmørgravJul 25, 2006 3:12 pm 
Eric AndersonJul 25, 2006 4:12 pm 
Shane AdamsJul 25, 2006 5:54 pm 
Rick C. PettyJul 25, 2006 6:33 pm 
Eric AndersonJul 25, 2006 6:39 pm 
Dag-Erling SmørgravJul 25, 2006 6:49 pm 
Dag-Erling SmørgravJul 27, 2006 7:14 am 
Rick C. PettyJul 27, 2006 5:54 pm 
Oliver FrommeJul 28, 2006 9:27 am 
Rick C. PettyJul 28, 2006 3:10 pm 
Shane AdamsAug 1, 2006 8:54 pm 
Eric AndersonAug 2, 2006 3:44 am 
Subject:Advice for hacking on ufs/ffs
From:Dag-Erling Smørgrav (de@des.no)
Date:Jul 25, 2006 3:12:50 pm
List:org.freebsd.freebsd-fs

Shane Adams <adam@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

-- Dag-Erling Sm?rgrav - de@des.no