> You write:
> 
> # Actually, I want to tell everyone and remind Chris of a problem we
> # ran into with libkern.
> # 
> # Chris wrote an LKM which he loaded into the kernel. It needed
> # strncpy, but strncpy is in libkern. Hence strncpy wasn't there,
> # and the LKM load failed.
> # 
> # This points out a rather silly problem with having these functions
> # be in libkern.. any thoughts from anyone?
> 
> Yeah, modify the LKM to also do some load-time linking with libkern...
> 
> Of course, this raises the isssue of "what can we chuck when we unload
> package X"...

Yes, I had this idea, too.

But the last question is a non-issue. If you unload a LKM you unload the
whole .o file which might contain functions like strncpy.
Since other LKMs are liked against /netbsd and not against the result of
loading the first LKM, they bring their own copy of strncpy if they need it.
--
ws@TooLs.DE     (Wolfgang Solfrank, TooLs GmbH) +49-228-985800

------------------------------------------------------------------------------