On Tue Sep 04, 2007 at 09:47:17 +0800, huang wrote:
When I tried to use the l4env nameserver "names" to help doing sth, I found it doesn't work. For example, the logserver "log" can not register at nameserver, so it fall asleep, so does names_demo. I examed and tested the names.c, and I modified a few lines of code in main() such as:
... if(rmgr_init()) printf("roottask service unavailable!\n"); else printf("roottask service init successfully!\n"); ...
then I rebuilded names, and tested again with modules listed in menu.lst:
title hello world kernel (hd0,0)/fiasco/bootstrap modaddr 0x02000000 module (hd0,0)/fiasco/fiasco -nokdb -nowait module (hd0,0)/fiasco/sigma0 module (hd0,0)/fiasco/roottask module (hd0,0)/fiasco/names module (hd0,0)/fiasco/names_demo
the output screen is in the attachement roottask.jpg, the key output is names | roottask service unavailable!
That's strange indeed. names_demo will not really work in this setup as it's querying for dm_phys which is not there (it's a demo). I cannot say why it does not work otherwise for you as it does for me. You could put your binaries online so that I can check what's going on (using tracing and similar).
Is this really caused by roottask??
In the manual tut.pdf, the menu.lst is as below:
title Hi world, server version kernel (nd)/tftpboot/yourname/bin/x86_586/l4v2/bootstrap modaddr 0x02000000 module (nd)/tftpboot/yourname/bin/fiasco -nokdb -nowait module (nd)/tftpboot/yourname/bin/x86_586/l4v2/sigma0 module (nd)/tftpboot/yourname/bin/x86_586/l4vs/roottask module (nd)/tftpboot/yourname/bin/x86_586/l4v2/log module (nd)/tftpboot/yourname/bin/x86_586/l4v2/names module (nd)/tftpboot/yourname/bin/x86_586/l4v2/dm_phys module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiserver module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiclient
I found the line of roottask is different from other lines in "l4vs", while others are "l4v2". What is the difference?
Just a typo, it's fixed internally.
Adam