Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!sri-spam!ames!ptsfa!hoptoad!academ!killer!jfh
From: jfh@killer.UUCP (John Haugh)
Newsgroups: comp.unix.questions
Subject: Re: A couple questions
Message-ID: <889@killer.UUCP>
Date: Fri, 15-May-87 12:37:19 EDT
Article-I.D.: killer.889
Posted: Fri May 15 12:37:19 1987
Date-Received: Sat, 23-May-87 04:24:09 EDT
References: <3164@jade.BERKELEY.EDU> <2382@ncoast.UUCP> <1752@dg_rtp.UUCP> <354@tdi2.UUCP>
Organization: The Unix(tm) Connection, Dallas, Texas
Lines: 31
Summary: Some files don't have names ...


Every one writes:
	yes - no - yes - no - yes - no.

Every one reads:
	confusion - confusion - confusion.

Some files have no name[s].  If the file descriptor is for one of those,
you ain't gonna get a name.  Files in this catagory that come to mind are
unnamed pipes, and files that have been removed.  You will never find a
name for these guys.

Some files have names that you can't access.  If you aren't root you can't
look everywheres for the directory names, unless your system permits it.
You may never find a name for these guys unless you are root.

Some files have more than one name.  You really only need one unless you
want to do something special, (like unlink it) since all links are equal
(except in BSD land).  You CAN find at least one name for these files.

Did I cover everything?  Lets put this one to rest.  Respond by E-Mail
rather than posting.  Also, somewheres I have a PD copy of ftw(3) - I
think someone posted one also a while ago.

- John.		(jfh@killer.UUCP)

Disclaimer -
	If my boss knew what USENET was, he'd want one of his own.

Favorite Borrowed Saying -
	"It's never too late for a happy childhood."