From owner-freebsd-current Sun Nov 7 19:19:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 0C70215109 for ; Sun, 7 Nov 1999 19:19:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from p138-ts5.syd2.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id OAA06681; Mon, 8 Nov 1999 14:24:38 +1100 Date: Mon, 8 Nov 1999 14:18:54 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: rm error code on FAT In-Reply-To: <38261A44.F0451032@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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