Date: Sun, 30 Dec 2001 12:09:16 EDT From: Eric Jacobs <eaja@erols.com> To: davidt@yadt.co.uk, freebsd-fs@freebsd.org Subject: Re: msdosfs_lookup returns EINVAL, not ENOENT Message-ID: <PstOfc.3c2f4a3c.c67ea6@localhost> In-Reply-To: <20011230161108.A76653@gattaca.yadt.co.uk> References: <20011230161108.A76653@gattaca.yadt.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
David Taylor <davidt@yadt.co.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PstOfc.3c2f4a3c.c67ea6>