Date: Mon, 8 Nov 1999 14:18:54 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Maxim Sobolev <sobomax@altavista.net> Cc: current@FreeBSD.ORG Subject: Re: rm error code on FAT Message-ID: <Pine.BSF.4.10.9911081351050.2071-100000@alphplex.bde.org> In-Reply-To: <38261A44.F0451032@altavista.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9911081351050.2071-100000>