This might help: <http://www.helpdesk.umd.edu/documents/1/1231/>
UNIX: How To Deal With Filenames Containing Unprintable/Special Characters Oscar At 05:30 PM 7/17/2002 -0400, [EMAIL PROTECTED], you wrote: >server /etc/namedb/ # ls -la |more >total 970 >-rw-r--r-- 1 bind bind - 552 Aug 8 2000 ^L >drwxr-xr-x 2 bind wheel - 10240 Jul 17 17:06 ./ >drwxr-xr-x 19 root wheel - 2560 Jul 17 17:20 ../ > >Can only be opened via (editor of choice) ?, e.g. pico ? > >The file contains a zone file, from ages ago, but the original zone file >is fine and >is still there. > >Even after a quick secondary backup of the whole directory, I am hesitant to >perform a rm ? because the directory contains 100's of critical zone files. > >Any safe way to remove it and why sometimes after an ls -la the file comes up >as ^L and other times ? and only can be opened when you specify ? > >Thank you! :) > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
