Date: Mon, 8 Nov 1999 18:39:23 -0600 From: "Matthew D. Fuller" <fullermd@futuresouth.com> To: Maxim Sobolev <sobomax@altavista.net> Cc: Bruce Evans <bde@zeta.org.au>, current@FreeBSD.ORG Subject: Re: rm error code on FAT Message-ID: <19991108183923.C393@futuresouth.com> In-Reply-To: <38276863.F71C2915@altavista.net> References: <Pine.BSF.4.10.9911081351050.2071-100000@alphplex.bde.org> <38276863.F71C2915@altavista.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" 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?19991108183923.C393>