Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!styx!ames!ucbcad!ucbvax!decvax!tektronix!uw-beaver!ssc-vax!cxsea!blm
From: blm@cxsea.UUCP
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.xenix
Subject: Re: Confused file name in directory
Message-ID: <2012@cxsea.UUCP>
Date: Sat, 28-Feb-87 13:42:18 EST
Article-I.D.: cxsea.2012
Posted: Sat Feb 28 13:42:18 1987
Date-Received: Mon, 2-Mar-87 06:42:22 EST
References: <105@aob.UUCP>
Reply-To: blm@cxsea.UUCP (Brian Matthews)
Organization: Computer X Inc.
Lines: 21
Xref: utgpu comp.unix.questions:1235 comp.unix.wizards:1184 comp.unix.xenix:134

In article <105@aob.UUCP> jim@aob.UUCP (Jim Anderson) writes:
|I have an Altos 2086 running XENIX 3.2f.  I had a problem show up recently
|that defies all my attempts to fix.  What has happened is that a file name
|in a directory has a null in the middle of the name.

I'm not familiar with XENIX, but System V has a utility called fsdb, that
let's you do strange and wonderous things to a file system, one of which is
to modify the name field of a directory entry. fsdb has to be run on an
unmounted file system, probably as superuser (if the permissions are set
up the way they should be on the file systems device). In my manual, the
second to last example is setting a file name.

If XENIX doesn't have fsdb, I guess I can't help you. clri/fsck is probably
the only way to go.

-- 

Brian L. Matthews                               "Facts are impotent against
...{mnetor,uw-beaver!ssc-vax}!cxsea!blm          loud and frequent assertion."
+1 206 251 6811
Computer X Inc. - a division of Motorola New Enterprises