[X-Unix] Re: Unlinking a file... illegal characters?

[Eric F Crist]

On Feb 26, 2005, at 5:18 AM, Stroller wrote:

>
> On Feb 26, 2005, at 10:48 am, Peter Dyballa wrote:
>
>>
>> Am 26.02.2005 um 03:24 schrieb=20
>> x-unix-request at listserver.themacintoshguy.com:
>>
>>> Would I be over-optimistic if I suggested that a different quoting
>>> method in the script might fix this?
>>
>> Since the Perl scripts can't print the file's name correctly, print=20=

>> must return an error code. If you catch this situation you have in=20
>> $inode the inode number of that file can unlink (delete) it in Perl.
>>
>> If you really want to know the file's name, catch the error condition=20=

>> too and print in a loop every character of this file in hex!
>>
>> This find
>>
>>      find /Volumes/CLEARLIGHT/.Trashes/501/legoland -type f -ls
>>
>> fails too?
>
> Unfortunately so. I've tried a few variations upon this already:
>
>   $ find /Volumes/CLEARLIGHT/foo/legoland -type f -ls
>   find: /Volumes/CLEARLIGHT/foo/legoland/e=ED=A5y=ED=C3y=ED=C3y=ED=C3vk=89=
=C6=A5=89=C6=A5..=89=C6=A5=89=C6=A5:=20
> File name too long
>   $ find /Volumes/CLEARLIGHT/foo/legoland -type f -print0
>   find: /Volumes/CLEARLIGHT/foo/legoland/e=ED=A5y=ED=C3y=ED=C3y=ED=C3vk=89=
=C6=A5=89=C6=A5..=89=C6=A5=89=C6=A5:=20
> File name too long
>
> So. I don't get far enough to identify the inode number using `find`.
>
> Stroller.

I know I'm coming into this kinda late, but have you tried, from the=20
containing directory of legoland:

/Volumes/CLEARLIGHT/foo/ # rm -rf ./legoland

This will delete the entire directory, and it's contents.

HTH
_______________________________________________________
Eric F Crist                  "I am so smart, S.M.R.T!"
Secure Computing Networks              -Homer J Simpson