Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: Bug in Ultrix2.0?
Message-ID: <6760@brl-smoke.ARPA>
Date: Sun, 29-Nov-87 03:14:18 EST
Article-I.D.: brl-smok.6760
Posted: Sun Nov 29 03:14:18 1987
Date-Received: Tue, 1-Dec-87 04:57:12 EST
References: <10570@brl-adm.ARPA>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 16

In article <10570@brl-adm.ARPA> "oread::barbanis"@CS-UMASS.arpa writes:
>$ ls -l foo baz  
>(foo does not exist, but baz is reported as having *two* links to it)

That's not a bug, that's exactly what I would expect.

Just because you were silly enough to lose the link to the directory
inode does not mean that you have affected the link count of inodes
that used to be located via that directory.

Unlinking a directory is restricted to the super-user in order to
maintain the integrity of the hierarchical file system structure.
It is not expected that privileged software would mess around with
this structure!

Run "fsck" to fix your messed-up filesystem before it's too late...