From owner-freebsd-fs Sun Dec 30 10: 6: 6 2001 Delivered-To: freebsd-fs@freebsd.org Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by hub.freebsd.org (Postfix) with ESMTP id 2F06937B405 for ; Sun, 30 Dec 2001 10:06:05 -0800 (PST) Received: from 66-44-21-127.s381.apx3.lnh.md.dialup.rcn.com ([66.44.21.127] helo=localhost.) by smtp02.mrf.mail.rcn.net with smtp (Exim 3.33 #10) id 16KkJu-0003hG-00; Sun, 30 Dec 2001 13:04:28 -0500 References: <20011230161108.A76653@gattaca.yadt.co.uk> In-Reply-To: <20011230161108.A76653@gattaca.yadt.co.uk> Date: Sun, 30 Dec 2001 12:09:16 EDT From: Eric Jacobs To: davidt@yadt.co.uk, freebsd-fs@freebsd.org Subject: Re: msdosfs_lookup returns EINVAL, not ENOENT Organization: X-Mailer: Post Office 0.7.2 build 20010211(by eric@localhost 2001/02/11 21:52:30) Message-ID: X-Mailer: PostOffice 0.7 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org David Taylor tapped some keys and produced: > > Whilst poking around on my msdosfs (trying to find an MP3 I thought I > had), I discovered that, if there are no files matching "foo*", ls foo* > will > return the wrong error. > > msdosfs: > > $ ls foo*=20 > ls: foo*: Invalid argument > > ufs: > > $ ls foo* > ls: foo*: No such file or directory > I noticed that too, and I like this behavior. I like having distinct errors to tell me not only when a required condition is false, but also when it couldn't possibly be true. -- P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message