Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: A couple questions
Message-ID: <6606@mimsy.UUCP>
Date: Sat, 9-May-87 10:55:39 EDT
Article-I.D.: mimsy.6606
Posted: Sat May  9 10:55:39 1987
Date-Received: Sun, 10-May-87 05:52:47 EDT
References: <3164@jade.BERKELEY.EDU> <2382@ncoast.UUCP> <1752@dg_rtp.UUCP> <1116@pompeii.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 27

>In article <6582@mimsy.UUCP> I wrote:
>>`find / -inum <n>' takes a *long* time on a big system.

In article <1116@pompeii.UUCP> schwartz@swatsun (Scott Schwartz) writes:
>But if you had to do it, wouldn't you use ncheck(8)? (Assuming you have
>the required permissions)

A dangerous assumption:

	% df /usr
	Filesystem    kbytes    used   avail capacity  Mounted on
	/dev/hp4a     182123  138994   24916    85%    /usr
	% ls -lg /dev/*hp4a
	brw-r-----  1 root     operator   0,  32 Oct 17  1986 /dev/hp4a
	crw-r-----  1 root     operator   4,  32 Apr 27 08:52 /dev/rhp4a
	% groups
	staff wheel daemon sys kmem operator uucp internet emacs zmob
	tex bridge mcmob info speech um-software
	%

Anyone can run `find /usr', but only root and group operator can
read the drive directly.  Had *I* to do it, I would indeed use
ncheck; but the average program seeking to tie a name to, e.g.,
stdin could not assume that ncheck would succeed.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris