Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!eneevax!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: A couple questions
Message-ID: <5835@brl-smoke.ARPA>
Date: Wed, 6-May-87 01:59:52 EDT
Article-I.D.: brl-smok.5835
Posted: Wed May  6 01:59:52 1987
Date-Received: Thu, 7-May-87 06:45:52 EDT
References: <3164@jade.BERKELEY.EDU> <2382@ncoast.UUCP> <1752@dg_rtp.UUCP> <816@killer.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 7

In article <816@killer.UUCP> jfh@killer.UUCP (John Haugh) writes:
>If you wanted to, you could even find out the name
>of the file that was connected to the descriptor.  (It is _not_ easy :-( )

I would think it's actually impossible.  The kernel doesn't remember
the name of the path you used to open an inode, and some descriptors
(e.g. pipes) have no associated names.