From owner-freebsd-hackers Thu Dec 19 03:29:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA16767 for hackers-outgoing; Thu, 19 Dec 1996 03:29:20 -0800 (PST) Received: from friley216.res.iastate.edu (friley216.res.iastate.edu [129.186.78.216]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA16761 for ; Thu, 19 Dec 1996 03:29:18 -0800 (PST) Received: from friley216.res.iastate.edu (loopback [127.0.0.1]) by friley216.res.iastate.edu (8.8.3/8.7.3) with ESMTP id FAA06565; Thu, 19 Dec 1996 05:26:50 -0600 (CST) Message-Id: <199612191126.FAA06565@friley216.res.iastate.edu> X-Mailer: exmh version 1.6.9 8/22/96 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@freebsd.org (FreeBSD hackers), reichert@internet.com Subject: Re: unlink by inodes? In-reply-to: Your message of Thu, 19 Dec 1996 07:46:43 +0100. <199612190646.HAA26525@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Dec 1996 05:26:50 -0600 From: Chris Csanady Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As michael butler wrote: > >> > 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, > >...short of running clri(8) and fsck(8). :-)) Yeah. :) You really should try to use the fs as it was intended anyway. BTW, does anyone know the status of McKusick's soft updates integration? I think this would make a lot of people happy.. --Chris Csanady > >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-)