home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.aix
- Path: sparky!uunet!mcsun!sun4nl!fwi.uva.nl!casper
- From: casper@fwi.uva.nl (Casper H.S. Dik)
- Subject: Re: NFS, /dev
- Message-ID: <1992Dec19.155204.20363@fwi.uva.nl>
- Keywords: NFS, mounting /dev
- Sender: news@fwi.uva.nl
- Nntp-Posting-Host: adam.fwi.uva.nl
- Organization: FWI, University of Amsterdam
- References: <Dec.11.19.30.18.1992.7849@remus.rutgers.edu> <BzBJA2.Apn@austin.ibm.com> <36694@sophia.inria.fr>
- Date: Sat, 19 Dec 1992 15:52:04 GMT
- Lines: 22
-
- rriv@oural.inria.fr (Robert Riviere) writes:
-
- >In article <BzBJA2.Apn@austin.ibm.com> curt@ekhadafi.austin.ibm.com (Curt Finch 903 2F021 curt@aixwiz.austin.ibm.com 512-838-2806) writes:
- >>
- >>You cannot use NFS to write to a device file across the network.
- >>NFS is stateless, which means the open() doesn't even go across the wire.
- >>Devices like to see their open()s so they can initialize and whatnot.
- >>
-
- >There is a thing about this which seems strange to me :
- >on some systems exists an mount option 'nodev' when mounting by NFS
-
- >What is it for ?
-
- Devices inodes on NFS filesystems are interpreted local to the machine.
- (E.g., /dev is NFS mounted on a diskless client). The nodev prevents
- this interpretation as it wuld give the superuser on the remote
- system the ability to create device nodes with permissions to
- his liking (e.g., /dev/mem, /dev/kmem) and compromise the integrity
- of the client. ``nodev'' is similar to nosuid.
-
- Casper
-