For a stat call you could argue either way: EINVAL because it's invalid,
ENOENT because the filesystem would never allow you to create an invalid
filename, so therefore it won't exist. OTOH a create/mkdir/mknod call
must return EINVAL, as it's the most specific error for the situation.
If the EINVAL is breaking commands, it seems to me it would be better to
map it to ENOENT where possible. The difference in file system semantics
makes some changes necessary, and we want msdos fs to be as useful as
possible.
I'd still like to know if this is a change in behavior from 2.0.xx
though.
Regards,
Bill