> But filename.bak or FILENAME.BAK or *.BAK, etc, are not invalid names
> under MS-DOS.
>
> The relatively new behavior makes scripts that contain :
> rm -f *.bak
> ... on a MS-DOS file-system fail because rm ignores ENOENT (only) when
> using the (f)orce option. I can modify rm, but this is not the correct
> fix.
Well, you can make a good argument that looking up an invalid filename
should result in ENOENT.
Is this a change in behavior for msdos fs? If so, we probably should
revert to the old behavior, unless someone has a good argument for
returning EINVAL.
Regards,
Bill