On Thu, 24 Feb 2000, Mike Smith wrote:
> > > I'd hazard a guess that the presence of modules is causing the kernel
> > > linker to run and pull all the sysctl hooks for modules it's finding.
> > > I'm probably wrong, just a guess.
> ...
> > I'll go look up cold usage, and see if it necessarily has to be done that
> > early. I'll also investigate that sysctl possibility.
>
> Oops. I meant sysinit, not sysctl.
Well, I don't think that's it. I've tried moving it around a bit.
None of the code is called until the intrhook handler is called back,
so I don't see how it can be the sysinit itself causing the failure.
> --
> \\ 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]
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED] `------------------------------'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
