Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!usc!cs.utexas.edu!uunet!mcsun!chsun!bernina!neptune!inf.ethz.ch!weingart From: weingart@inf.ethz.ch (Tobias Weingartner) Subject: Re: Some ideas on the driver interface (New idea!) Message-ID: <1993Mar22.135730.8173@neptune.inf.ethz.ch> Followup-To: comp.os.386bsd.development, poster Sender: news@neptune.inf.ethz.ch (Mr News) Nntp-Posting-Host: antares.inf.ethz.ch Reply-To: weingart@inf.ethz.ch Organization: ETH - Switzerland References: <1993Mar17.122612.5929@neptune.inf.ethz.ch> <1o9l9u$nn@tricky.wft.stack.urc.tue.nl> Date: Mon, 22 Mar 1993 13:57:30 GMT Lines: 23 In article <1o9l9u$nn@tricky.wft.stack.urc.tue.nl>, michael@wft.stack.urc.tue.nl (Michael Brouwer) writes: > In article <1993Mar17.122612.5929@neptune.inf.ethz.ch> weingart@inf.ethz.ch > (Tobias Weingartner) writes: > > There. Simple no? Instead of making mount(2) take a special file, > > make it take a string representing the device. The "dev" device would > > be mounted on /dev, and emulate like it was a real /dev. This way > > only the devices that were configured into the kernel would even > > need to show up in "dev". > > This is a really nice idea, but you'll have to think of a way to implement > things like `chgrp uucp /dev/com01'; `chmod 660 /dev/com01', or do you suggest > rebuilding the kernel to modify `/dev' protection? No, the kernel (or driver) emulates the 'dev' device just like /dev. If you do a chmod or chown or whatever, it will get reflected on the device. Hmm, makes me wonder what an rm or mknod would do... ;-) --Toby. Tobias Weingartner * PGP2.1 Public Key available at * +41'41'33'25'40 * 'finger weingart@tau.inf.ethz.ch' * %SYSTEM-F-ANARCHISM, the operating system has been overthrown