From owner-freebsd-current Sun Nov 7 16:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 44FA014EC5 for ; Sun, 7 Nov 1999 16:34:34 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-5.iptelecom.net.ua [212.9.226.5]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id CAA07498 for ; Mon, 8 Nov 1999 02:37:17 +0200 (EET) Message-ID: <38261A44.F0451032@altavista.net> Date: Mon, 08 Nov 1999 02:33:08 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: rm error code on FAT Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. bash-2.03# mount /dev/ad0s2a on / (ufs, local, noatime, soft-updates, writes: sync 231 async 5542) procfs on /proc (procfs, local) /dev/ad0s1 on /mnt (msdos, local) bash-2.03# rm /tmp/*.no_such_files rm: /tmp/*.no_such_files: No such file or directory bash-2.03# rm /mnt/*.no_such_files rm: /mnt/*.no_such_files: Invalid argument -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message