Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: nyu notesfiles V1.1 4/1/84; site rna.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!zehntel!hplabs!hao!seismo!cmcl2!rna!dan
From: dan@rna.UUCP
Newsgroups: net.unix
Subject: Re: How can I find where a link leads to
Message-ID: <11000006@rna.UUCP>
Date: Sun, 20-Jan-85 20:22:00 EST
Article-I.D.: rna.11000006
Posted: Sun Jan 20 20:22:00 1985
Date-Received: Mon, 14-Jan-85 04:39:54 EST
References: <719@hou2h.UUCP>
Lines: 16
Nf-ID: #R:hou2h:-71900:rna:11000006:000:643
Nf-From: rna!dan    Jan 11 20:22:00 1985

> ls -i filename
> gives you the inode number; otherwise the question has no meaning.
> All links have the same status; there is no place in the
> hierarchical file system where the file "really" is.

But it is often helpful to find out what are the other pathnames of the
file/inode in question. This is possible with ncheck:

	ncheck -i #### /dev/xxx

where ### is the inode number of the file you want to find all the pathnames
to and /dev/xxx is the special device name of the filesystem on which the
file/inode resides. However, on some systems ncheck and/or /dev/xxx is
protected and non-root people can't perform the above...

					Dan