Andy Hassall wrote:[color=blue]
> On Mon, 02 Aug 2004 13:07:07 GMT, Michael Austin <maustin@firstdbasource.com>
> wrote:
>
>[color=green]
>>One thing that MS has really messed up is allowing spaces and certain
>>meta-characters in file names.[/color]
>
>
> Unix filesystems are typically MORE liberal than FAT32 and NTFS with regards
> to filenames; the only invalid characters are chr(0) (NUL) and the directory
> separator /.
>
> andyh@server:~/tmp$ cat makeIckyFile.pl
> #!/usr/bin/perl
> my $fn;
> $fn = join '', grep {$_ ne '/'} map {chr} (1..255);
> open my $fp, '>', "tmp/$fn"
> or die $!;
>
> andyh@server:~/tmp$ ./makeIckyFile.pl
> andyh@server:~/tmp$ ls -l tmp/
> total 0
> -rw-r--r-- 1 andyh users 0 Aug 2 21:03
> \001\002\003\004\005\006\a\b\t\n\v\f\r\016\017\020 \021\022\023\024\025\026\027\030\031\032\033\034\0 35\036\037\
> !"#$%&'()\*+,-.0123456789:;<\=>?\@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{\|}~\177\200\201\202 \203\204\205\206\207\210\211\212\213\214\215\216\2 17\220\221\222\223\224\225\226\227\230\231\232\233 \234\235\236\237\240\241\242\243\244\245\246\247\2 50\251\252\253\254\255\256\257\260\261\262\263\264 \265\266\267\270\271\272\273\274\275\276\277\300\3 01\302\303\304\305\306\307\310\311\312\313\314\315 \316\317\320\321\322\323\324\325\326\327\330\331\3 32\333\334\335\336\337\340\341\342\343\344\345\346 \347\350\351\352\353\354\355\356\357\360\361\362\3 63\364\365\366\367\370\371\372\373\374\375\376\377
>[/color]
You are of course correct, for whatever reason I had another filesystem on my
brain - RMS.
"icky" is a mild understatement for a description of that filename...
--
Michael Austin.
Consultant - Available.
Donations welcomed.
Http://www.firstdbasource.com/donations.html
:)