pesky file alarm

[Super user]

I run a 286 box with SCO Xenix 2.2.something and I have a weird one
for you:
________________________________________________________________________

# cd /usr/spool
# ls -il
./c not found		<<< that's the alarm bell
total 52
   48 drwxrwxrwx   2 news     root          64 Aug 30 10:08 batch
   60 drwxr-xr-x   4 root     root          64 Aug 26 14:06 cron
[ ... ]
# > c
# ls -il
total 54
   48 drwxrwxrwx   2 news     root          64 Aug 30 10:08 batch
  236 -rw-r--r--   1 root     root           0 Aug 30 21:46 c <<< that's
    4 -rw-r--r--   1 root     root           0 Aug 30 21:46 c <<< a riot
   60 drwxr-xr-x   4 root     root          64 Aug 26 14:06 cron
[ ... ]
# ls | hd
0000	62 61 74 63 68 0a 63 0a  63 0a 63 72 6f 6e 0a 69   batch.c.c.cron.i
[ ... ]
004f
# rm c
# ls -il
./c not found		<<< that's the alarm bell again
total 52
   48 drwxrwxrwx   2 news     root          64 Aug 30 10:08 batch
   60 drwxr-xr-x   4 root     root          64 Aug 26 14:06 cron
[ ... ]
# mount
/dev/root on / read/write on Sun Aug 28 08:31:31 1988
/dev/spooler on /usr/spool read/write on Sun Aug 28 08:31:35 1988
[ ... ]
#
________________________________________________________________________

It is not shown above, but there is a lost+found directory.
What now appears as a pesky file named c, used to be the cron directory
until my system got zapped by lightning (modem slagged).  I am lucky
there is no more damage than that but I'd like to know what happened
and how to repair it, if possible.  I recreated a cron directory but
I really don't know if I should have.

As usual, mail your replies please, I'll summarize them here.

Alain
							  (514) 486 5980
William Alain Simon - 5418 Grovehill Place - Montreal - H4A 1J9 - Canada
{...!mcgill-vision!{odyssee|iros1}|...!uunet!attcan!s