From owner-freebsd-current Wed Apr 12 12:40:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA21545 for current-outgoing; Wed, 12 Apr 1995 12:40:43 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA21539 for ; Wed, 12 Apr 1995 12:40:42 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id MAA09915; Wed, 12 Apr 1995 12:40:39 -0700 From: Poul-Henning Kamp Message-Id: <199504121940.MAA09915@ref.tfs.com> Subject: Re: Attention device-driver writers! To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Wed, 12 Apr 1995 12:40:38 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <9504121934.AA07483@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 12, 95 03:34:05 pm Content-Type: text Content-Length: 636 Sender: current-owner@FreeBSD.org Precedence: bulk > I recently made another apss through all the device drivers in > preparation for adding another variable for devconf. (I might also > partially re-design the way devconf and sysctl interface; it could use > some improvement, but I'm not likely to have the time.) Garrett, I think you could save yourself a lot of grief it you actually wrote the "What is devconf and why should my device care" FAQ. The documentation is slightly thin in this area... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'