On Sun, 16 Nov 2003 [EMAIL PROTECTED] wrote:
It looks like the kldload system call takes the name of the module you
give it, like ums, and just tacks on .ko and searches
in whatever the default paths are for kernel modules until it finds
ums.ko. Peachy.
But what about if you built your
On 2003-11-17 at 18:47:28 Doug White wrote:
If you give a specific path to a module then it will load that module.
No. It will not load arbitrary files, but _only_ files that end in
.ko. I've encountered this before, and therefore I always simply
follow a make installkernel.debug by a script
It looks like the kldload system call takes
the name of the module you give it, like ums, and just tacks on .ko and searches
in whatever the default paths are for kernel modules until it finds ums.ko. Peachy.
But what about if you built your kernel and modules with debugging symbols added in?
