Date: Mon, 12 Jul 2004 17:23:50 -0500 From: Jason Dusek <jason-dusek@uiowa.edu> To: current@freebsd.org Subject: Re: kldload won't load Message-ID: <40F30F76.3000602@uiowa.edu> In-Reply-To: <Pine.NEB.3.96L.1040712174751.52015G-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040712174751.52015G-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
So, the problem is *not* that kldload can not find the file? There is something new at the bottom of my dmesg: link_elf: symbol device_get_sysctl_ctx undefined What's this mean and how do I fix ndis? - Jason Robert Watson wrote: > On Mon, 12 Jul 2004, John Polstra wrote: > > >>On 12-Jul-2004 Doug Rabson wrote: >> >>>Hmm. Maybe the simplest thing would be to print the link errors using >>>uprintf() instead of printf(). >> >>That's a good idea. It would be a lot better than what we have now. > > > If possible, we should printf() as well, since linker errors may not > happen in the context of a supervising user. I.e., during the boot > process, etc. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Research > > > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40F30F76.3000602>