Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.unix.questions
Subject: Re: A couple questions
Message-ID: <18252@sun.uucp>
Date: Thu, 7-May-87 02:07:26 EDT
Article-I.D.: sun.18252
Posted: Thu May  7 02:07:26 1987
Date-Received: Fri, 8-May-87 05:36:27 EDT
References: <3164@jade.BERKELEY.EDU> <2382@ncoast.UUCP> <1752@dg_rtp.UUCP> <634@boulder.Colorado.EDU>
Sender: news@sun.uucp
Lines: 15

> actually, it is possible. you know the inode associated with the descriptor
> start at "/" and just keep looking for that i# keeping track of where you
> are.

No, Doug is correct.  In the general case, it is *not* possible -
there may not *be* a directory entry that refers to the inode in
question.  The inode may be an unnamed pipe, or may be a file that
was unlinked.  Even if there is a directory entry that refers to the
inode in question, it is not possible if you lack read permission on
any of the directories leading up to that file.

Furthermore, given the procedure you suggest, it may be technically
possible in many cases but it is not practical in many, probably
most, of them.  Doing a top-down search for a given inode, starting
at "/", can take a *very* long time unless you're very near the root.