Date: Mon, 12 Jul 2004 17:00:58 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: John Polstra <jdp@polstra.com> Cc: freebsd-current@freebsd.org Subject: Re: kldload won't load Message-ID: <Pine.NEB.3.96L.1040712170028.52015F-100000@fledge.watson.org> In-Reply-To: <XFMail.20040712135543.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Jul 2004, John Polstra wrote: > > Well, the problem here is that the errno error-reporting mechanism can > > report but not describe errors. We could add a new EKLDLINKER to point at > > a linker error (or the like), or a whole set of new errnos, but the > > mechanism even then couldn't report which symbols are missing, etc. One > > or more linker-specific error values would probably be a useful start. > > I fully understand the implementation difficulties, but we have to be > careful to observe the distinction between correct behavior and > easy-to-implement behavior. The kldload(2) API doesn't support correct > behavior, so that's where the focus needs to be -- not on making users > feel stupid for failing to look in the dmesg output. I don't disagree, but you have to admit that the kitten dying thing is a interesting (if unusual) side effect. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040712170028.52015F-100000>