Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!manuel.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!wupost!howland.reston.ans.net!usc!sdd.hp.com!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!menudo.uh.edu!uuneo!sugar!peter From: peter@NeoSoft.com (Peter da Silva) Subject: Re: Some ideas on the driver interface (was: Re: Release of drivers etc.) Organization: NeoSoft Communications Services -- (713) 684-5900 Date: Wed, 3 Mar 1993 17:40:25 GMT Message-ID: <C3BqFG.1q3@sugar.neosoft.com> References: <C32vAt.3t9.1@cs.cmu.edu> <C3AL86.Kt5@cs.mcgill.ca> <1993Mar3.104035.13082@gmd.de> Lines: 16 In article <1993Mar3.104035.13082@gmd.de> veit@fanoe.gmd.de (Holger Veit) writes: > The question is whether to provide > special "files" (say inodes with special attributes set) by the user > (by creating it via mknod) or by the system itself (which "knows" about the > drivers in it), and represent this information about the devices in a > "device file system". Special files, unless the device itself requires something more exotic, in which case you mount that device on /dev/something. That way you can change what's in /dev directly, like putting a socket endpoint in there, without having to define a whole new set of namespace interactions. -- Peter da Silva. <peter@sugar.neosoft.com>. `-_-' Oletko halannut suttasi tänään? 'U` Tarjoilija, tämä ateria elää vielä.