Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!dcdwest!ittvax!decvax!genrad!panda!talcott!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix,net.unix-wizards,net.bugs.usg
Subject: Re: Null in directory name
Message-ID: <4415@umcp-cs.UUCP>
Date: Fri, 29-Mar-85 03:10:09 EST
Article-I.D.: umcp-cs.4415
Posted: Fri Mar 29 03:10:09 1985
Date-Received: Tue, 2-Apr-85 05:24:18 EST
References: <32@wcom.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 16
Xref: watmath net.unix:4082 net.unix-wizards:12668 net.bugs.usg:205

Adb (or---if you're lucky enough to have one---a file system scribble
tool program) can correct mucked up directory names.

However, (and I'm not sure if works for System n, where 3 <= n <= 5),
there is a better way:  if /usr is corrupted such that /usr/bin is now
/usr/b^@n, then "ln /usr/b" to "/usr/bin".  This works iff your namei
code doesn't compare the entire name, including all trailing nulls.
Unfortunately, most do.

As a third alternative, you can always "mkdir /usr/bin" and restore
only the files that go there (assuming you have plenty of disk space),
then remove the "/usr/b^@n" later.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland