Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site axiom.UUCP
Path: utzoo!linus!axiom!smk
From: smk@axiom.UUCP (Steven Kramer)
Newsgroups: net.unix-wizards
Subject: Re: file access
Message-ID: <468@axiom.UUCP>
Date: Wed, 18-Jan-84 16:26:57 EST
Article-I.D.: axiom.468
Posted: Wed Jan 18 16:26:57 1984
Date-Received: Thu, 19-Jan-84 01:41:47 EST
References: <15625@sri-arpa.UUCP>
Organization: Axiom Technology, Newton MA
Lines: 19

I think you're missing something.  If you can read the directory
as a whole or name by name, you are obtaining the SAME information.
If protection of the directory disallows reading, you cannot read
anything on either method.  (I assume on the name by name system
call basis you will also get the inode number, which makes both
methods eqivalent.)  In fact, the opendir(), ... 4.2BSD (compatible)
library routines do EXACTLY what you want, but alas, the protection
is exactly the same on either method.

So, directly, UNIX gives you the `raw' directory file to look at,
and you can build routines around the structure to make your life
easier.  That's the UNIX way.  (I know by saying things like this
last statement I'll get a rebuttal.  For this article, I'll only
take rebuttals from North Dakota [is there one?] -- the rest of you
flame to /dev/null.)
-- 
	--steve kramer
	{allegra,genrad,ihnp4,utzoo,philabs,uw-beaver}!linus!axiom!smk	(UUCP)
	linus!axiom!smk@mitre-bedford					(MIL)