Hi Volkmar,
I did this because I wanted to keep the kernel debugger but I didn't found out how to use it to resume booting. Try "h" for help - it shows you a list of all kdb commands - isn't that "*nix"-like? Well, I've found out that 'g' was the right key. Of course, I tried 'h' at first, but due to some screen handling bug, only a part of the help screen appeared.
Meanwhile, I've done some hacking on bochs sources and was able to boot L4Ka with the template root_task. As already mailed, bochs' and l4ka' patches as well as some screen shots are available under: http://home.kamp.net/home/farid.hajji/l4ka-bochs/ Once screen shot demonstrates what I mean about messed up screen handling.
The Linux's module overlaps with needed physical ram. That overlapping can be avoided by forcing grub to load the modules at a different address (a hack which made it into Dresden's GRUB distribution or use our GRUB-disk). I added an x86-FAQ-page with a description: http://l4ka.org/faq/x86.asp Was that GRUB-hack committed to CVS at subversions.gnu.org? I used the most recent GRUB sources.
Thanks, -Farid. -- Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555 Broicherdorfstr. 83, D-41564 Kaarst, Germany | farid.hajji@ob.kamp.net - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - Murphy's Law fails only when you try to demonstrate it, and thus succeeds.