>
> If I have a KLD module that has a registered dependency on some other
> module,
> then when I load the forst module it will load the second.
> this is all well and good but it ALWYA loads it,
> even when it's already in the kernel..
>
> if kldstat can see it, then surely the loading modules should be able to
> work it out.
>
> This has been partly fixed in -current (it loads but doesn't link)
> but in 3.x it actually links the new one over the existing one,
> which is kinda wrong..
>
> Is there anyone that understands this stuff that has an idea of ho to fix
> this?
Yes. See my posts previously on making the distinction between 'file'
and 'module'. You've just acquired some new programming talent there;
I'm sure I could dope out enough of what was worked out last time we
talked about this to give her something to work on. 8)
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
