Hi Ernst, my apologies for not responding to your intriguing problem before.
> However if I use wildcards, for instance doing a DIR *.TXT (and > ofcourse there are a number of .TXT files present) no files are shown > and File Not Found is the error message shown by the DIR command. > (.TXT is just an example, any (part of) the filename, any extension > and any combination of the two wildcards * and ? always delivers the > samen result: file not found). This is quite bizarre. I can assume that Windows / SMB filesharing moves the interpreting of the wildcards to the server, explaining why the server can break it. In any case, I've managed to reproduce this problem on my 2.0g. It seems to be independent of the filesystem used, it breaks on NTFS, FAT and ext2. I first tested on a 2.0n, where everything works as expected. Given that both devices run the same samba version, I suspect there is some kernel bug causing this problem (introduced between 2.6.21 and 2.6.26, the 2.0n's kernel is older). I haven't dug into this issue yet, just tried to reproduce it. To help us keep track of this bug, could you perhaps create a ticket on http://trac.fonosfera.org with the information you provided? Regards, Matthijs Kooijman _______________________________________________ Development mailing list [email protected] http://fonosfera.org/mailman/listinfo/development
