Re: [RFC] More meaningful information about ENOEXEC for kldload(8)

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: John Baldwin
Date: Tuesday, October 26, 2010 - 6:26 am

On Monday, October 25, 2010 3:19:26 pm Xin LI wrote:

The reason I vote know is that ENOEXEC can mean several things.  I thought you 
had a patch to catch the actual kernel error message and pass it back to 
userland.  That would be a useful feature, but this message doesn't really 
help and can point people in the wrong direction if their error is due to a 
different problem.

If you want to help the user, then I think a more useful approach would be to
tell the user to check dmesg for error messages when kldload(2) fails with 
ENOEXEC.

-- 
John Baldwin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [RFC] More meaningful information about ENOEXEC for kl ..., John Baldwin, (Tue Oct 26, 6:26 am)
Strange hang HPET in current , Andrey Smagin, (Wed Oct 27, 12:33 am)
Re: Strange hang HPET in current, Alexander Motin, (Fri Oct 29, 6:55 am)
Re: Strange hang HPET in current, Alexander Motin, (Fri Oct 29, 7:04 am)