Re: How do I keep testing current-amd64 witout so much trouble?

[christos%astron.com@localhost (Christos Zoulas)]

In article <Pine.NEB.4.64.0812250715440.12440%quicky.whooppee.com@localhost>,
Paul Goyette  <paul%whooppee.com@localhost> wrote:
>On Wed, 24 Dec 2008, Paul Goyette wrote:
>
>> On Wed, 24 Dec 2008, Steven M. Bellovin wrote:
>>
>>> I haven't tried any systems with loadable modules yet -- does 'boot -a'
>>> let you specify the module path?
>>
>> I don't think so, but it sounds to me like a useful enhancement.
>
>I actually tried to do this, but ran into a little problem.  :)
>
>I added a prompt in sys/kern/kern_module.c routine module_init() (based 
>on setting of RB_ASKNAME flag in global variable boothowto), and set the 
>value of module_base to the user's answer.  This part worked.  However, 
>all subsequent prompts triggered by RB_ASKNAME just hung.  Keyboard was 
>unresponsive (both USB keyboard and PS/2 keyboard).
>
>I suspect that calling cngetsn() at the time of module_init() is leaving 
>something in a bad state.  Perhaps cngetsn() needs something else to 
>happen first.  But I couldn't find any better place to put the prompt 
>for module_base.

Try a lockdebug kernel. I get spinouts when I do that.

christos