From owner-freebsd-doc  Thu Aug  3 16:48:19 1995
Return-Path: doc-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id QAA07961
          for doc-outgoing; Thu, 3 Aug 1995 16:48:19 -0700
Received: from tserv.lodgenet.com (dial4.iw.net [204.157.148.53])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA07926
          for <doc@freebsd.org>; Thu, 3 Aug 1995 16:46:53 -0700
Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id SAA24353; Thu, 3 Aug 1995 18:47:26 -0500
Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.6.11/8.6.9) with SMTP id SAA13365; Thu, 3 Aug 1995 18:46:11 -0500
Message-Id: <199508032346.SAA13365@jake.lodgenet.com>
X-Authentication-Warning: jake.lodgenet.com: Host localhost didn't use HELO protocol
X-Mailer: exmh version 1.6 4/21/95
To: Wilko Bulte <wilko@yedi.iaf.nl>
cc: doc@freebsd.org
Subject: Re: device driver writers guide 
In-reply-to: Your message of "Thu, 03 Aug 1995 22:11:24 +0200."
             <199508032011.WAA01172@yedi.iaf.nl> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 03 Aug 1995 18:46:09 -0500
From: "Eric L. Hernes" <erich@lodgenet.com>
Sender: doc-owner@freebsd.org
Precedence: bulk

> > > One of the issues in BSD is lack of documentation for internal
> > > system interfaces.  VM would be a good place to start, as would
> > > vn_ for kernel level file I/O and bXXX, the block I/O interface.
> > > 
> > 
> > Yea, but lack of documentation is a problem for all unixes.
> > Sco, even though you can pay for a device driver class, and
> > they have man pages for kernel support routines, still
> > is about 80% of what I would have liked.  (that is still
> > much better than FreeBSD, though)
> 
> And they have a nice little booklet called the 'Device
> drivers writers guide' (if memory serves). I heavily used
> it when writing a striping package for SCO. 
> 

Yup, the name is stolen.  Sco has one, and I've seen linux has
a doc by that name too.  There are probably several others.

> The list you mention of things to be doc-ed looks 
> reasonably like the index of the SCO book as I remember it.
> 
Well, that may be just coincidence, or it may not be.  I've got the book on 
my shelf here, but I didn't look at it when I scribbled that draft.
Its mostly what I remembered from the class, and how I thought
things should have been done.

> Another point of inspiration might be the 'Integrated
> software development guide' that came with SysV/386 rel 3.2
> There is probably a newer one for SysV4
> 

Never seen it, but I'd be interested.

> > > 					Terry Lambert
> > 
> > erich@lodgenet.com
> 
> Wilko
> 
> _     __________________________________________________________________________
>  |   / o / /  _   Wilko Bulte             email: wilko@yedi.iaf.nl
>  |/|/ / / /( (_)  Private FreeBSD site  - Arnhem - The Netherlands
> --------------------------------------------------------------------------------
> 

--
erich@lodgenet.com
erich@rrnet.com