Eugen Hristev <eugen.hristev@xxxxxxxxxxxxx> writes: > Okay, I am changing it. > > By the way, is this supposed to work like this on case-insensitive directories ? > > user@debian-rockchip-rock5b-rk3588:~$ ls -la /media/CI_dir/*cuc > ls: cannot access '/media/CI_dir/*cuc': No such file or directory > user@debian-rockchip-rock5b-rk3588:~$ ls -la /media/CI_dir/*CUC > -rw-r--r-- 1 root root 0 Feb 12 17:47 /media/CI_dir/CUC > user@debian-rockchip-rock5b-rk3588:~$ ls -la /media/CI_dir/cuc > -rw-r--r-- 1 root root 0 Feb 12 17:47 /media/CI_dir/cuc > user@debian-rockchip-rock5b-rk3588:~$ > > > basically wildcards don't work. Yes, at least from a kernel point of view. Your shell does wildcards in userspace, probably by doing getdents and then comparing with possible matches. Since the shell itself is not case-insensitive aware, its comparison is case-sensitive, and you get these apparent weird semantics. Not ideal from a user point of view. But not a kernel bug. If it pushes people away from using case-insensitive directories in their day-to-day work and leave it to only be used by Windows compatibility layers, maybe that's a win? :) -- Gabriel Krisman Bertazi
