On Mon, 8 Nov 1999, Maxim Sobolev wrote:
> Does anybody can explain why two absolutely identical attempts to remove
> unexistent files on UFS and FAT32 yields different error codes ("No such
> file or directory" and "Invalid argument" respectively)? This breaks "rm
> -f" behaviour, because instead of expected "0", "rm -f" on FAT returns
> error code instead.
unlink("/mnt/*.no_such_files") on msdosfs returns EINVAL because the
pathname contains the invalid character '*'. EINVAL used to be a
documented errno for pathnames containing characters with their high
bit set). This documentation should have been made filesystem-
dependent instead of removing it.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
