Path: utzoo!mnetor!uunet!husc6!ukma!rutgers!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.unix.questions
Subject: Re:  Accessing files by inode #s
Message-ID: <2050@bsu-cs.UUCP>
Date: 6 Feb 88 23:07:42 GMT
References: <11667@brl-adm.ARPA>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 18
Summary: 8th bit set in filename

In article <11667@brl-adm.ARPA> wmartin@almsa-1.arpa (Will Martin -- AMXAL-RI)
writes:
>An "ls -l ?ol?" will get "cannot stat hold" as the response. Notice that
>the commands can say "hold" in these cases, and not "?ol?". They CAN find
>this file, but they then cannot work upon it. An "od -c ." will
>produce output in which I can find the offending file with its name
>interpreted as "350 o l 344". 

It looks like the eighth bit is set in "h" and "d" in the filename.  It
may be that you rm program ignores the 8th bit and tries to remove (or
stat) "hold" in 7-bit ascii, or that the shell expands your wildcards
in 7-bit ascii only.

I suggest the following C program:

     main() { unlink ("\350ol\344"); }
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!dhesi