Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!ames!oliveb!sun!gorodish!guy
From: guy@gorodish.UUCP
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.xenix
Subject: Re: Confused file name in directory
Message-ID: <14115@sun.uucp>
Date: Thu, 26-Feb-87 05:17:39 EST
Article-I.D.: sun.14115
Posted: Thu Feb 26 05:17:39 1987
Date-Received: Sat, 28-Feb-87 05:16:40 EST
References: <105@aob.UUCP> <563@aw.sei.cmu.edu.sei.cmu.edu> <5587@mimsy.UUCP>
Sender: news@sun.uucp
Reply-To: guy@sun.UUCP (Guy Harris)
Organization: Sun Microsystems, Mountain View
Lines: 10
Xref: utgpu comp.unix.questions:1197 comp.unix.wizards:1139 comp.unix.xenix:123

>Of course, if you have source, you could alter fsck to check for
>embedded NULs in filenames.

And not to *generate* file names with embedded NULs.  Some versions
of "fsck" for the V7 file system (as used in most UNIX systems not
using the 4.2BSD file system) would assume that any free directory
slot in "lost+found" would have no non-NUL characters in the
directory name portion of that slot, which is not the case.  The V7
and System III versions did not zero out the entire file name; this
is fixed in S5.  Check the routine "mkentry".