Hi Jason ! >For what it's worth the users with this problem were unable to >remove the files using wildcards.
This most likely happen for the star operator. Use correct number of question marks at correct position. This gives better results. > For example, one user had a >file named: > > På hjul.mkv > >ls P* displayed the file. >rm P* returned the error "can't remove 'På Hjul.mkv': No such >file or directory" Yes this happens if rm does a directory scan then does some editing of the file name before using it. The biggest problem here is, when the name contains characters that can't be displayed or are used as control characters. may be a find -name PATTERN -delete helps or a find -name PATTERN -print0 | xargs -0 rm >I have been unable to find other reports of problems like this. >Perhaps it is unlucky that BusyBox just happened to be 2 for 2! This is a well known problem which exists since there where different code pages and character sets for different national characters used to create file names on different file systems. Those files are either created from other systems (may be using samba) or are the result of untar/unzip/unrar of files packed on Windows systems ... and there exist a few characters which get really problematic when they get entered into file names, but that's the mess with different code pages and file systems. Since we have wide spread UTF-8 things seam to get better, but still such shit happens (saying this, just got trouble after unpacking a Zip-File, looks like it was packaged under Windows, now I have files with none readable characters in my directory, nothing has to do with busybox). -- Harald _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
