Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncrcae.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!ncsu!ncrcae!vause
From: vause@ncrcae.UUCP (Sam Vause)
Newsgroups: net.unix
Subject: Re: Bizzare Filenames
Message-ID: <2158@ncrcae.UUCP>
Date: Tue, 14-May-85 23:43:52 EDT
Article-I.D.: ncrcae.2158
Posted: Tue May 14 23:43:52 1985
Date-Received: Sun, 19-May-85 00:53:48 EDT
References: <10612@brl-tgr.ARPA>
Reply-To: vause@ncrcae.UUCP (Sam Vause)
Organization: NCR, Columbia, SC
Lines: 12
Summary: 

In article <10612@brl-tgr.ARPA> howell@MITRE.ARPA (Chuck Howell) writes:
>> What happens if one (by mistake) creates a file called `ctl-foo' and one
>> didn't know that this was happening.  The next time they did an `ls'
>> of that directory they'd get a `?' and it would be impossible to remove
>> because they don't know the name.
>
>If you really want to know the (non-printing) characters in your 
>filename, you can always ls > somefile.tmp, then vi (or emacs, or
>od -c, or whatever...) somefile.tmp.  [This works on ULTRIX anyway].

One (perhaps less-than-obvious) method of getting rid of weird files is by
the judicious use of "rm -i *".  Sure gets rid of the Klingons!