> > 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. -- \\ 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
- Re: After last ATAPI update system doesn't boot ... Mike Smith
- Re: After last ATAPI update system doesn't boot ... Soren Schmidt
- Re: After last ATAPI update system doesn't boot ... Doug Rabson
- Re: After last ATAPI update system doesn't boot ... Soren Schmidt
- Re: After last ATAPI update system doesn't boot ... Benno Rice
- Re: After last ATAPI update system doesn't boot ... Yarema
- Re: After last ATAPI update system doesn't boot ... Mike Smith
- Re: After last ATAPI update system doesn't boot ... Soren Schmidt
- Re: After last ATAPI update system doesn't boot ... Mike Smith
- Re: After last ATAPI update system doesn't boot ... Brian Fundakowski Feldman
- Re: After last ATAPI update system doesn't boot ... Mike Smith
- Re: After last ATAPI update system doesn't boot ... Brian Fundakowski Feldman
- Re: After last ATAPI update system doesn't boot ... Doug Barton
- Re: After last ATAPI update system doesn't boot ... Warner Losh