From owner-freebsd-doc  Thu Aug  3 16:25:53 1995
Return-Path: doc-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id QAA06893
          for doc-outgoing; Thu, 3 Aug 1995 16:25:53 -0700
Received: from linux4nn.iaf.nl (linux4nn.iaf.nl [193.67.144.34])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id QAA06887
          for <doc@freebsd.org>; Thu, 3 Aug 1995 16:25:50 -0700
Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.iaf.nl (8.6.9/8.6.9) with SMTP id BAA10862; Fri, 4 Aug 1995 01:33:11 +0200
Received: by uni4nn.iaf.nl with UUCP id AA16495
  (5.67b/IDA-1.5); Fri, 4 Aug 1995 01:25:20 +0100
Received: by iafnl.iaf.nl with UUCP id AA05435
  (5.65c/IDA-1.4.4); Thu, 3 Aug 1995 22:59:20 +0200
Received: (from wilko@localhost) by yedi.iaf.nl (8.6.8/8.6.6) id WAA01172; Thu, 3 Aug 1995 22:11:25 +0200
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199508032011.WAA01172@yedi.iaf.nl>
Subject: Re: device driver writers guide
To: erich@lodgenet.com (Eric L. Hernes)
Date: Thu, 3 Aug 1995 22:11:24 +0200 (MET DST)
Cc: terry@cs.weber.edu, doc@freebsd.org
In-Reply-To: <199508031523.KAA10229@jake.lodgenet.com> from "Eric L. Hernes" at Aug 3, 95 10:23:38 am
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1393      
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. 

Unfortunately, it is all but complete. We needed the SCO
kernel sources to get things working. Luckily we had a
src license..

The list you mention of things to be doc-ed looks 
reasonably like the index of the SCO book as I remember it.

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

> > 					Terry Lambert
> 
> erich@lodgenet.com

Wilko

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