From owner-freebsd-hackers  Wed Dec 18 20:18:57 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id UAA28536
          for hackers-outgoing; Wed, 18 Dec 1996 20:18:57 -0800 (PST)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA28530
          for <freebsd-hackers@freebsd.org>; Wed, 18 Dec 1996 20:18:54 -0800 (PST)
Received: (from imb@localhost)
          by asstdc.scgt.oz.au (8.7.6/BSD4.4) id PAA22239
          Thu, 19 Dec 1996 15:18:40 +1100 (EST)
From: michael butler <imb@scgt.oz.au>
Message-Id: <199612190418.PAA22239@asstdc.scgt.oz.au>
Subject: Re: unlink by inodes?
In-Reply-To: <19961219031216.27145.qmail@oneida.internet.com> from Brian Reichert at "Dec 18, 96 10:12:16 pm"
To: reichert@internet.com (Brian Reichert)
Date: Thu, 19 Dec 1996 15:18:40 +1100 (EST)
Cc: freebsd-hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Brian Reichert writes:

> Howdy, folks -
 
> Is there a way of unlinking a file, given it's _inode_ ?  I was
> exploring news expiration alternatives, and was wondering how to
> avoid the overhead of path -> inode lookup...

Consider that you must find each directory referencing this inode in order
to remove the (possibly multiple) entries pointing to it,

	michael