Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site x.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!think!mit-eddie!cybvax0!frog!x!john
From: john@x.UUCP (John Woods)
Newsgroups: net.unix
Subject: Re: Funny filenames: so far, no good... (2.9BSD)
Message-ID: <520@x.UUCP>
Date: Thu, 30-May-85 10:51:12 EDT
Article-I.D.: x.520
Posted: Thu May 30 10:51:12 1985
Date-Received: Sat, 1-Jun-85 12:54:28 EDT
References: <1163@uwmacc.UUCP>
Distribution: net
Organization: Charles River Data Systems, Framingham MA
Lines: 27

> I've had a number of responses on how to remove the file whose name is
> 	\t 360 200 035 002 \0
> but no one has won yet.  Most people recommended using unlink(2) like this:
> 	main() {
> 		unlink("\t\360\200\035\002");
> 	}
> but this fails. 	...
> That failed too.  Holy filename, Batman!  What next?
> 	Jeff Percival ...!uwvax!uwmacc!jwp

If that fails, you must have the "`feature'" turned on where 2.9 strips
out "`illegal'" characters in file names.  If so, you have one-and-a-half
options:
(.75)  Go to your kernel sources, remove that feature, bulk-erase your
distribution tape so it will never come back, recompile and reboot.  Then
do the unlink, unmolested by malfeatures.
(1.5)  Open the raw disk for writing with adb.  When I have to patch disks
by hand, I always print up extra copies of section 5 of the manual to
have them arrayed in front of me...

If you don't have sources, you're stuck with the second.  Neither of them
is enjoyable, but at least the first cures it forever.
-- 
John Woods, Charles River Data Systems, Framingham MA, (617) 626-1101
...!decvax!frog!john, ...!mit-eddie!jfw, jfw%mit-ccc@MIT-XX.ARPA

"MU" said the Sacred Chao...