Date: Wed, 05 Aug 2009 15:50:19 +0200 From: Dimitry Andric <dimitry@andric.com> To: Mel Flynn <mel.flynn+fbsd.hackers@mailing.thruhere.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Spot the error Message-ID: <4A798E1B.9010109@andric.com> In-Reply-To: <200908041615.49128.mel.flynn%2Bfbsd.hackers@mailing.thruhere.net> References: <200908041245.35926.mel.flynn%2Bfbsd.hackers@mailing.thruhere.net> <4A78AB7C.3040406@andric.com> <200908041615.49128.mel.flynn%2Bfbsd.hackers@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-08-05 02:15, Mel Flynn wrote: > I would expect "Unable to load fs: " + ENOENT. I was asking if this was > fixable, cause it looked like the code has been abstracted to the point that > specific errors were hard, but maybe I missed something. It does not seem easily fixable. The problem is that the mount command simply prints out the error of the system call, and doesn't have any idea which of the (many) parameters was wrong. You could change the returned error in this particular case to ENOENT, of course, but that might be considered even more confusing. Like, "What do you mean, that SCSI disk doesn't exist? It's right there in /dev!" One could also argue for EINVAL, but there's the bikeshed again... :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A798E1B.9010109>