From owner-freebsd-questions Thu Feb 26 17:58:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22785 for freebsd-questions-outgoing; Thu, 26 Feb 1998 17:58:11 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22709 for ; Thu, 26 Feb 1998 17:57:53 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id RAA00918; Thu, 26 Feb 1998 17:57:50 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Thu, 26 Feb 1998 17:57:50 -0800 (PST) From: Doug White Reply-To: Doug White To: Mark Castillo cc: freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD programming - kernel and device drivers In-Reply-To: <199802261557.KAA13290@spades.relationships.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Feb 1998, Mark Castillo wrote: > I have been using FreeBSD since 2.1 and programmed C for 4 years and no > assembly experience. I am interested in writing device drivers and kernel > coding. What kind of books and resources should one read to get started in > system level programming for FreeBSD? Please advise to a budding FreeBSD > hacker. Well, thankfully, you don't really need assembly to write drivers to hack kernels. The quintisential hacker's guidebook is ``The Design and Implementation of 4.4BSD'', available cheaply from Amazon.com or your favorite bookstore. Next is the source itself :) and a tutorial at http://www.freebsd.org/tutorials/ddwg. Finally is the freebsd-hackers mailing list. Hope that helps, and enjoy! Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message