Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!usc!samsung!uunet!brunix!sgf
From: sgf@cs.brown.edu (Sam Fulcomer)
Newsgroups: comp.sys.sgi
Subject: Re: Dangling inode problem
Message-ID: <58544@brunix.UUCP>
Date: 5 Dec 90 15:55:11 GMT
References: <1990Dec1.194910.9878@portia.Stanford.EDU> <srp.660086900@babar.mmwb.ucsf.edu> <1990Dec5.032329.5531@odin.corp.sgi.com>
Sender: news@brunix.UUCP
Reply-To: sgf@cs.brown.edu (Sam Fulcomer)
Organization: Brown University Department of Computer Science
Lines: 11

In article <1990Dec5.032329.5531@odin.corp.sgi.com> bh@sgi.com (Bent Hagemark) writes:
>
>Yes, fsck properly clears the reference, and yes nothing else can.

Well, let's be fair now... It wouldn't be hard to edit the directory (by 
some means other than fsck) directly through the disk driver. It's just that,
since most OS implementations somewhat prudishly disallow write() to dir,
no other approach can work. (except perhaps a good, swift kick) 


_/**/Sam