From owner-freebsd-hackers  Sun Oct 20 11:03:23 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA05016
          for hackers-outgoing; Sun, 20 Oct 1996 11:03:23 -0700 (PDT)
Received: from darling.cs.umd.edu (10862@darling.cs.umd.edu [128.8.128.115])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA05011
          for <freebsd-hackers@freebsd.org>; Sun, 20 Oct 1996 11:03:21 -0700 (PDT)
Received: by darling.cs.umd.edu (8.7.6/UMIACS-0.9/04-05-88)
	id OAA27834; Sun, 20 Oct 1996 14:02:51 -0400 (EDT)
Message-Id: <199610201802.OAA27834@darling.cs.umd.edu>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-hackers@freebsd.org (FreeBSD hackers)
Subject: Re: Conventions/Rules for adding Local ioctls 
In-reply-to: Your message of "Sun, 20 Oct 1996 09:10:17 +0200."
             <199610200710.JAA27702@uriah.heep.sax.de> 
Date: Sun, 20 Oct 1996 14:02:50 -0400
From: Rohit Dube <rohit@cs.umd.edu>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 20 Oct 1996 09:10:17 +0200 (MET DST) j@uriah.heep.sax.de writes:
=>You must avoid the `f' group (FIOxxx, see <sys/filio.h>) since the
=>generic ioctl code handles them first, independently of the underlying
=>driver.
=>
=>You must avoid any of the cmds your driver intends to pass on to
=>underlying physical devices (by directly calling their ioctl entry
=>point).

Thanks for your reply.

=>
=>> I was hoping for a globally maintained file hidden somewhere which listed
=>> at least the 'taken' groups. More comments??
=>
=>We will happily include it somewhere in the documentation if you write
=>this file.  (no smiley, no joke!)

Ok, I'll try to cook this over the next couple of days as I look thru the
various.h files to make sure that I don't conflict with other code.

=>
=>Of course, don't be surprised, with only 2*26 letters, it's very
=>likely that several groups are already in duplicate use.
=>

Hmmmmm.

--rohit.