Date: Mon, 25 Oct 2010 17:53:36 -0700 From: Garrett Cooper <gcooper@FreeBSD.org> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: [RFC] More meaningful information about ENOEXEC for kldload(8) Message-ID: <AANLkTinoQR1KGbwL3m-Gbc5zi2drbJ_XhsxaqnKfuhKz@mail.gmail.com> In-Reply-To: <4CC5F35A.7090809@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
> 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 ran into this `item' (:)..) today after a power outage because
nvidia-driver was built against different kernel headers, and it
prints out the error clear as day on /dev/console, so I'm tempted to
say that documenting the behavior is enough as long as it's clear that
that is in fact the behavior that the user is dealing with :).
Thanks!
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinoQR1KGbwL3m-Gbc5zi2drbJ_XhsxaqnKfuhKz>