Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site turtlevax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!pesnta!amd!turtlevax!ken
From: ken@turtlevax.UUCP (Ken Turkowski)
Newsgroups: net.unix
Subject: Re: Funny filenames: so far, no good... (2.9BSD)
Message-ID: <781@turtlevax.UUCP>
Date: Tue, 4-Jun-85 15:28:21 EDT
Article-I.D.: turtleva.781
Posted: Tue Jun  4 15:28:21 1985
Date-Received: Thu, 6-Jun-85 06:15:27 EDT
References: <1163@uwmacc.UUCP> <520@x.UUCP>
Reply-To: ken@turtlevax.UUCP (Ken Turkowski)
Distribution: net
Organization: CADLINC, Inc. @ Menlo Park, CA
Lines: 30

In article <520@x.UUCP> john@x.UUCP (John Woods) writes:
>> 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.

You can also zap the inode with clri, and let fsck remove it.
-- 

Ken Turkowski @ CADLINC, Menlo Park, CA
UUCP: {amd,decwrl,hplabs,nsc,seismo,spar}!turtlevax!ken
ARPA: turtlevax!ken@DECWRL.ARPA