From owner-freebsd-current Tue Nov 9 11:29:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from pulsar.dead-end.net (pulsar.high-performance.com [216.15.153.82]) by hub.freebsd.org (Postfix) with ESMTP id 7643214EA1 for ; Tue, 9 Nov 1999 11:29:20 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.153.82] (may be forged)) by pulsar.dead-end.net (8.9.3/8.9.3/DEAD-END/1999020900) with ESMTP id UAA24539; Tue, 9 Nov 1999 20:27:46 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9E0E8F.dip.t-dialin.net [62.158.14.143]) by mailto.dead-end.net (8.9.3/DEAD-END/1999102400-Customer) with ESMTP id UAA24519; Tue, 9 Nov 1999 20:27:40 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (solaris.rock.net [172.23.7.10]) by server.rock.net (8.9.3/8.9.3/ROCK/1999053100) with ESMTP id UAA15181; Tue, 9 Nov 1999 20:27:59 +0100 (CET) (envelope-from rock@dead-end.net) Message-ID: <382875A7.FE47C781@dead-end.net> Date: Tue, 09 Nov 1999 20:27:35 +0100 From: "D. Rock" X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: Maxim Sobolev Cc: "Matthew D. Fuller" , Bruce Evans , current@FreeBSD.ORG Subject: Re: rm error code on FAT References: <38276863.F71C2915@altavista.net> <19991108183923.C393@futuresouth.com> <382774CD.2305EDDA@altavista.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > "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.... Wildcards only get expanded by the shell if there is something to expand. Just write an "echo" instead of "rm" for your command and see by yourself. csh would show the error message "no match", but sh compatible shells just display: # mkdir empty # cd empty # echo *xtra *xtra So in fact, if you try to remove something, the '*' is indeed part of the filename for the unlink() command. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message