Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!houxm!hropus!jgy
From: jgy@hropus.UUCP (jgy)
Newsgroups: net.unix-wizards,net.sources.bugs
Subject: Re: What happens during an unlink(2)
Message-ID: <442@hropus.UUCP>
Date: Tue, 6-May-86 17:22:24 EDT
Article-I.D.: hropus.442
Posted: Tue May  6 17:22:24 1986
Date-Received: Thu, 8-May-86 21:41:22 EDT
References: <947@kitty.UUCP> <403@ukecc.UUCP> <979@kitty.UUCP> <422@ukecc.UUCP>
Organization: Bell Labs, Holmdel, NJ
Lines: 12
Keywords: ``Relink'' April Fool
Xref: watmath net.unix-wizards:17971 net.sources.bugs:832

Someone said:
> When you unlink a file, the disk block addresses in the inode are
> zeroed, not the actual data blocks. Zeroing the inode is tantamount to
> 'forgetting' where the data is actually stored. ..............

This is not true, all that is necessary is that the blocks be put on the
freelist, the inode marked unallocated and added to the inode freelist.
If this were the case you could just go and look at your unallocated inode
for the block information. The onus would be on the system to clear the
inode before being reused. The only possible dispute I can see with this
is (problems with a crash can be handled) that of who should be
"charged" with clearing of someone else's dirty inode!