Date: Mon, 25 Oct 2010 23:35:52 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Garrett Cooper <gcooper@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: [RFC] More meaningful information about ENOEXEC for kldload(8) Message-ID: <4CC676C8.8070303@FreeBSD.org> In-Reply-To: <AANLkTinoQR1KGbwL3m-Gbc5zi2drbJ_XhsxaqnKfuhKz@mail.gmail.com> References: <4CC5D83E.8030505@delphij.net> <4CC5D9DB.1020409@FreeBSD.org> <AANLkTindYRwpmA=En%2BpYyHVcUkmQ0wsZrB7Y-f2E=vK=@mail.gmail.com> <ia4pjg$650$1@dough.gmane.org> <4CC5F35A.7090809@FreeBSD.org> <AANLkTinoQR1KGbwL3m-Gbc5zi2drbJ_XhsxaqnKfuhKz@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/25/2010 5:53 PM, Garrett Cooper wrote: > On Mon, Oct 25, 2010 at 2:15 PM, Doug Barton<dougb@freebsd.org> wrote: >> On 10/25/2010 13:33, Ivan Voras wrote: >>> >>> (except if the message is changed to say "please look at the kernel >>> syslog messages to find out the real reason for this failure") >> >> Thinking about Garrett's response as well, this may be the best way to go. > > Well.. I'm not saying the current output is the best, but I just > don't want to dig a deeper hole that will further confuse people, as > some users may get even more confused with additional details. I don't think "You'll find more information in the logs" to be confusing. >> At this point I'm also not concerned about waiting for an ideal solution. >> IMO an incremental change here would be most welcome. > > Wouldn't noting this in the manpage be sufficient? I think _also_ adding it to the man page would be appropriate. IMO this is an area where we have to try and think more like users, and less like developers. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CC676C8.8070303>