>From: Robert Elz <kre@munnari.OZ.AU>
>     Date:        Thu, 4 Apr 2002 00:34:13 -0800 (PST)
>     From:        "Simon J. Gerraty" <sjg@crufty.net>
>     Message-ID:  <200204040834.AAA04860@zen.crufty.net>
> 
>   | FWIW I had a case like that many years ago.
>   | Solution was to clri the file, let fsck map it into lost+found
>   | and mv to a sane name.
> 
> More likely what you did was to move all other files out of the directory
> containing the bad name, and then clri the directory.   Then you have an
> unreferenced inode which is otherwise just fine, and which fsck will link
> into lost+found (after which you can mv it somewhere more useful).

Now that you mention it, that does sound more like what happened - it
was 10+ years ago :-)  I definitely recall grumbling about letting
appletalk on the net if that was going to be the result :-)

> This message is really just for the archives, in case someone ever has
> this problem, goes searching, and (apparently) gets told the right thing
> to do is to clri the inode of the file with the bad name...  (it isn't).

Indeed.  Thanks for picking that up.
--sjg