Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxj!mhuxr!ulysses!allegra!bellcore!decvax!cca!ima!pbear!peterb From: peterb@pbear.UUCP Newsgroups: net.unix Subject: Re: 'dot' file deleted! Message-ID: <73@pbear.UUCP> Date: Fri, 1-Mar-85 02:43:39 EST Article-I.D.: pbear.73 Posted: Fri Mar 1 02:43:39 1985 Date-Received: Mon, 4-Mar-85 04:14:12 EST Lines: 16 Nf-ID: #R:hound:-95700:pbear:27800001:000:687 Nf-From: pbear!peterb Feb 27 14:59:00 1985 One possiblity is to ls -i the file to get the inode, and then have your guru (or someone else who will take the blame) to clri that inode. Then run fsck to reclaim the logically lost space. This ought to work, but I am not guarenteeing anything. Remember, only do this on an UNMOUNTED file system else havoc can reak and make thy life not worth the disk space used to record it! And make sure that you fsck the file system afterwords else the filesystem gets lost and the data goes to trash and you suddenly have lots of people ready to turn you into lots of tiny pieces. How in hell does . vanish ??? I thought fsck catches these things. Peter Barada ima!pbear!peterb