Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!brutus.cs.uiuc.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.questions
Subject: Re: fcntl
Message-ID: <12351@smoke.BRL.MIL>
Date: 15 Mar 90 00:18:39 GMT
References: <1990Mar13.125755.9720@granite.cr.bull.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <1990Mar13.125755.9720@granite.cr.bull.com> freedman@granite.cr.bull.com (Jerome Freedman) writes:
>  I know what the entry point(s) to ioctl are (I've seen
>enough drivers but where are the fcntl entry points?
>There is sort of an overlap there. Will a fcntl cause
>a call to dev_ioctl?

Well, it's not supposed to -- fcntl() was introduced specifically
to play with the file table entries, which is something the device
driver is not supposed to know (or care) about.