From owner-freebsd-current Mon Nov 8 17:13:30 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 CAADB1523D for ; Mon, 8 Nov 1999 17:13:22 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup6-60.iptelecom.net.ua [212.9.227.124]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id DAA17033; Tue, 9 Nov 1999 03:15:47 +0200 (EET) Message-ID: <382774CD.2305EDDA@altavista.net> Date: Tue, 09 Nov 1999 03:11:41 +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: "Matthew D. Fuller" Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: rm error code on FAT References: <38276863.F71C2915@altavista.net> <19991108183923.C393@futuresouth.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew D. Fuller" wrote: > On Tue, Nov 09, 1999 at 02:18:44AM +0200, a little birdie told me > that Maxim Sobolev remarked > > > > If your logic is right, then attempt to remove existent files from FAT using > > '*' should yield absolutely the same result (i.e. EINVAL). But in fact files > > being removed from FAT w/o any problems (touch /fat/1.exist /fat/2.exist ; rm > > /*.exist). IMHO it is clear bug in unlink error codes on FAT f/s. > > I think you'll find that the '*' in that case is expanded by your shell > long before rm ever gets to it. *sigh* (seems it is time for me to go into the bed ;). You are probably right - it seems I forgot to take into account shell role. So it is pure and unavoidable "feature" of FAT.... -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message