l4-hackers January 2008

l4-hackers@os.inf.tu-dresden.de

19 participants
45 discussions

Runux script to run Fiasco-UX
by Lucyantie Mazalan 30 Jan '08

30 Jan '08

Hi, | | | It should be "./fiasco -l hello". | | | | When I try (to run existing module), I get this: | | | | ---------------------------------------------------------------------- | | -- | | ---- | | root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# ./fiasco -l | | hiworld | | | | | | Fiasco-UX on Linux 2.6.20-15-generic (i686) Mapped 64 MB Memory + 0 KB | | Framebuffer + 0 MB Input Area on FD 3 | | | | Loading Module 0x00100000-0x00109364 [sigma0] Loading Module | | … [View More]0x00110000-0x002af000 [roottask] Failed to open file: hiworld | | root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# | That's how it should look like. The error tells you that the hiworld binary is missing or has inappropriate rights. (Btw.: You're still building as | root...) Thanks I have copied my binaries and it runs well. | You might want to have a look at the scripts in l4/tool/runux - there is also a config file template which you can adapt for your system. Then you don't | always need to copy around your binaries. I am now trying to find the mentioned script but could not find it in my l4/tool/runux. Here is what I have: ----------------------------------------------------------------- lucy@lucy-ubuntu:/home/fiasco/l4/tool$ ls bin config gendep Makefile lucy@lucy-ubuntu:/home/fiasco/l4/tool$ slocate runux /home/fiasco/build/doc/bid-tut/hi-runux.tex /home/fiasco/l4/mk/.svn/prop-base/runux.mk.svn-base /home/fiasco/l4/mk/.svn/text-base/runux.mk.svn-base /home/fiasco/l4/mk/runux.mk /home/fiasco/l4/doc/bid-tut/.svn/prop-base/hi-runux.tex.svn-base /home/fiasco/l4/doc/bid-tut/.svn/text-base/hi-runux.tex.svn-base /home/fiasco/l4/doc/bid-tut/hi-runux.tex ----------------------------------------------------------------- Is there anything I should do beforehand? According to http://os.inf.tu-dresden.de/l4env/doc/html/bid-tut/tut.pdf, I have to edit the hello file in l4/tool/runux to start Fiasco-UX which will also start my server & client binaries. I have found the same script but it is named as 'hi-runux.tex' and it is in different path - /home/fiasco/build/doc/bid-tut/-. Any help? Anyone? Thanks in advance, Lucille. ------------------------------------------------------------------ - - - DISCLAIMER: This e-mail (including any attachments) may contain confidential information. If you are not the intended recipient, you are hereby notified that any dealing, review, distribution, printing, copying or use of this e-mail is strictly prohibited. If you have received this email in error, please notify the sender or MIMOS Berhad immediately and delete the original message. Opinions, conclusions and other information in this e-mail that do not relate to the official business of MIMOS Berhad and/or its subsidiaries shall be understood as neither given nor endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS Berhad nor its subsidiaries accepts responsibility for the same. All liability arising from or in connection with computer viruses and/or corrupted e-mails is excluded to the fullest extent permitted by law. [View Less]

2 1

Re: error in writing code for IPC servers & problem with Fiasco-UX
by Björn Döbel 29 Jan '08

29 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lucyantie Mazalan wrote: | Hi again, thanks for replying. | | | Did you build your package's include directory before building the | | client dir? | | Yes definitely, I built my include dir first before building the client | dir. anything else should be wrong? I don't get your error here. The only thing that's wrong in your tgz is that you link the client against libaes256.a, but your lib is called libaes.a | | It should be "./fiasco -l hello". | … [View More]

2 1

Re: menu.lst for running flips in L4
by Björn Döbel 29 Jan '08

29 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, | Thanks all. Finally everything works fine! | I can now ping my fiasco machine from other linux machine. Is there any way | that I can ping other PC from my Fiasco machine? Fine. There is no ping tool in l4/pkg yet, but you may now use FLIPS to build your own one (or port an existing one). | If I set up 2 fiasco machines under my dhcp-enabled network environment, can | it ping each other? There's no reason why this shouldn't work. Regards,… [View More]

2 4

Re: error in writing code for IPC servers & problem with Fiasco-UX
by Bjoern Doebel 29 Jan '08

29 Jan '08

Hello, [..] > However, when I compile again my client code, I still got the same error which makes me more confused of where is actually the problem is. Here I attach the pkg archive and paste the errors that I get: > > ---------------------------------------------------------------------------- > root@lucy-ubuntu:/# cd home/fiasco/l4/pkg/aes/examples/client/ > root@lucy-ubuntu:/home/fiasco/l4/pkg/aes/examples/client# make O=/home/fiasco/build/ > PWD=/home/fiasco/build/pkg/… [View More]aes/examples/client/OBJ-x86_586-l4v2 make -C /home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2 -f Makefile > make[1]: Entering directory `/home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2' > ... Compiling main.o > LD_PRELOAD=/home/fiasco/build/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -m32 -c -DUSE_UCLIBC=y -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/fiasco/build/pkg/aes/idl/OBJ-x86-l4v2 -I/home/fiasco/build/include/x86/l4v2 -I/home/fiasco/build/include/l4v2 -I/home/fiasco/build/include/x86 -I/home/fiasco/build/include -I/home/fiasco/l4/../dice/include -I/home/drops/include/x86/l4v2 -I/home/drops/include/l4v2 -I/home/drops/include/x86 -I/home/drops/include -nostdinc -I/home/fiasco/build/include/x86/uclibc -I/home/fiasco/build/include/uclibc -I/home/fiasco/build/include/uclibc++ -I/home/drops/include/x86/uclibc -I/home/drops/include/uclibc -I/home/drops/include/uclibc++ -I/usr/lib/gcc/i486-linux-gnu/3.4.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common /home/fias co/l4/pkg/aes/examples/client/main.c -o main.o > /home/fiasco/l4/pkg/aes/examples/client/main.c:4:51: home/fiasco/l4/pkg/aes/include/aes256.h: No such file or directory > make[1]: *** [main.o] Error 1 > make[1]: Leaving directory `/home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2' > make: *** [/home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2] Error 2 > root@lucy-ubuntu:/home/fiasco/l4/pkg/aes/examples/client# > ---------------------------------------------------------------------------- Did you build your package's include directory before building the client dir? > Second, regarding using Fiasco-UX: > > I have configured, compile kernel and copied down all the binaries (fiasco, irq0, roottask, sigma0) into one folder in a way to build and use Fiasco-UX by referring to: > http://os.inf.tu-dresden.de/fiasco/ux/building.shtml > I exclude ux_con binary as it is an optional. However, this is what I get when I try to run a module: > > ---------------------------------------------------------------------------- > root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# ls > fiasco irq0 roottask sigma0 > root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# fiasco -l hello > -bash: fiasco: command not found It should be "./fiasco -l hello". Bjoern [View Less]

1 0

FW: error in writing code for IPC servers & problem with Fiasco-UX
by Lucyantie Mazalan 29 Jan '08

29 Jan '08

Hi, Thanks for the reply. With this email I hope to resolve my previous problems and also seek for solution of new problem. First, to respond you from previous email: | * your package dir is called aes, so all include files need to be | included through something like <l4/aes/...> Yes, previously my package name was that but I rename the archive file name to aes for your reference. But, however I am now sending to you the fixed one which all the include path is exactly same as the … [View More]package name, aes. Sorry for that. | * the IDL file somehow needs to know about your aes_context type, so | either include it from a header or define it inside the IDL file - I did | so by uncommenting your stuff. Thank you, yes I have fixed it by defining the aes_context type inside the IDL file. I have also recompiled it; generate new server code and writing new same implementation in my server's functions. | And this was probably your problem: | - ---> | * The aes-client.h file should be included using | ~ #include "aes-client.h" | ~ without any directory prefixes. It is a generated header file which | ~ does not end up in the L4 include dir, but resides inside the | ~ package's IDL build dir. This is path is different from the usual | ~ include paths and is added to your compile run automatically by BID. Thank you for the information. Yes I have also fixed in my aes package file which includes the header with just a '#include "aes-client.h"', without the prefixes. However, when I compile again my client code, I still got the same error which makes me more confused of where is actually the problem is. Here I attach the pkg archive and paste the errors that I get: ---------------------------------------------------------------------------- root@lucy-ubuntu:/# cd home/fiasco/l4/pkg/aes/examples/client/ root@lucy-ubuntu:/home/fiasco/l4/pkg/aes/examples/client# make O=/home/fiasco/build/ PWD=/home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2 make -C /home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2 -f Makefile make[1]: Entering directory `/home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2' ... Compiling main.o LD_PRELOAD=/home/fiasco/build/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -m32 -c -DUSE_UCLIBC=y -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/fiasco/build/pkg/aes/idl/OBJ-x86-l4v2 -I/home/fiasco/build/include/x86/l4v2 -I/home/fiasco/build/include/l4v2 -I/home/fiasco/build/include/x86 -I/home/fiasco/build/include -I/home/fiasco/l4/../dice/include -I/home/drops/include/x86/l4v2 -I/home/drops/include/l4v2 -I/home/drops/include/x86 -I/home/drops/include -nostdinc -I/home/fiasco/build/include/x86/uclibc -I/home/fiasco/build/include/uclibc -I/home/fiasco/build/include/uclibc++ -I/home/drops/include/x86/uclibc -I/home/drops/include/uclibc -I/home/drops/include/uclibc++ -I/usr/lib/gcc/i486-linux-gnu/3.4.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common /home/fiasco/l4/pkg/aes/examples/client/main.c -o main.o /home/fiasco/l4/pkg/aes/examples/client/main.c:4:51: home/fiasco/l4/pkg/aes/include/aes256.h: No such file or directory make[1]: *** [main.o] Error 1 make[1]: Leaving directory `/home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2' make: *** [/home/fiasco/build/pkg/aes/examples/client/OBJ-x86_586-l4v2] Error 2 root@lucy-ubuntu:/home/fiasco/l4/pkg/aes/examples/client# ---------------------------------------------------------------------------- Second, regarding using Fiasco-UX: I have configured, compile kernel and copied down all the binaries (fiasco, irq0, roottask, sigma0) into one folder in a way to build and use Fiasco-UX by referring to: http://os.inf.tu-dresden.de/fiasco/ux/building.shtml I exclude ux_con binary as it is an optional. However, this is what I get when I try to run a module: ---------------------------------------------------------------------------- root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# ls fiasco irq0 roottask sigma0 root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# fiasco -l hello -bash: fiasco: command not found root@lucy-ubuntu:/home/fiasco/kernel/fiasco/build-ux# ---------------------------------------------------------------------------- What might be the errors I falls in? Many thanks. Lucille. -----Original Message----- From: Björn Döbel [mailto:doebel@os.inf.tu-dresden.de] Sent: Thursday, January 24, 2008 18:52 To: Lucyantie Mazalan; l4-hackers(a)os.inf.tu-dresden.de Subject: Re: BID-coding an encapsulate -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, | | 1st - why do you build as root? | | Owh, I didn't realize it could affect me more of this privilege. There is no need to build as root and it's usually security risk. | | Ok. So aes_aes256_init is a function defined by your wrapper library? In | this case you should also link your wrapper lib to your application. | This can be done by adding | | | LIBS += -laesclient | | | to the example client's Makefile. | | I did this, but still no clue :( | I attach the archive, thank you. Ok, builds for me after some fixes: * your package dir is called aes, so all include files need to be included through something like <l4/aes/...> * the IDL file somehow needs to know about your aes_context type, so either include it from a header or define it inside the IDL file - I did so by uncommenting your stuff. And this was probably your problem: - ---> * The aes-client.h file should be included using ~ #include "aes-client.h" ~ without any directory prefixes. It is a generated header file which ~ does not end up in the L4 include dir, but resides inside the ~ package's IDL build dir. This is path is different from the usual ~ include paths and is added to your compile run automatically by BID. <--- Regards, Bjoern - -- Dipl.-Inf. Bjoern Doebel Mail: doebel(a)tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmG3aP5ijxgQLUNkRApYXAJ0TMW3ic1bPGVp7UAFRF1QrV0MiagCeJVs/ GZhEKQfn0Eqt60XTaOVCEIU= =keed -----END PGP SIGNATURE----- ------------------------------------------------------------------ - - - DISCLAIMER: This e-mail (including any attachments) may contain confidential information. If you are not the intended recipient, you are hereby notified that any dealing, review, distribution, printing, copying or use of this e-mail is strictly prohibited. If you have received this email in error, please notify the sender or MIMOS Berhad immediately and delete the original message. Opinions, conclusions and other information in this e-mail that do not relate to the official business of MIMOS Berhad and/or its subsidiaries shall be understood as neither given nor endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS Berhad nor its subsidiaries accepts responsibility for the same. All liability arising from or in connection with computer viruses and/or corrupted e-mails is excluded to the fullest extent permitted by law. [View Less]

1 0

Question about semaphores and threads
by Marc CHALAND 28 Jan '08

28 Jan '08

Hi, Sometimes, I get the following message : semaphore/lib/src/semaphore.c:167:__enqueue_thread(): Error : l4semahore: failed to get priority of thread 17.08: invalid argument (-3) Into sources, the comment says that thread has not been created by l4thread or is dead. But all threads are created by l4thread and no one is explicitly killed by another thread. Is there a mechanism which kills threads ? Is it possible a lock is requested as thread is not completely created ? Anybody has got an … [View More]

3 8

RE: January 71% OFF
by l4-hackers＠os.inf.tu-dresden.de 28 Jan '08

28 Jan '08

1 0

What's wrong with my l4con
by fei li 28 Jan '08

28 Jan '08

These days I have tested l4con on my machine. First I just move the l4con package into my L4Linux directory and modify my menu.lst, but I can't get the result. Then I copy the menu.lst from the wiki, and it's ok. Now I have several questions and hope someone helps me. This is my own menu.lst title L4Linux26/Fiasco+dope #root (hd0,7) kernel /boot/L4Linux/bootstrap modaddr 0x06000000 #module /boot/L4Linux/main -nowait -nokdb module /boot/L4Linux/fiasco -nokdb -… [View More]serial_esc module /boot/L4Linux/sigma0 module /boot/L4Linux/roottask task modname "bmodfs" attached 7 modules module /boot/L4Linux/events module /boot/L4Linux/names --events module /boot/L4Linux/log --events module /boot/L4Linux/dde26_test module /boot/L4Linux/dm_phys --isa=0x00800000 -v --events module /boot/L4Linux/simple_ts -t 300 --events module /boot/L4Linux/rtc --events module /boot/L4Linux/l4io --noirq --events module #module /boot/L4Linux/omega0 --l4io #module /boot/L4Linux/l4dope #module /boot/L4Linux/proxygon module /boot/L4Linux/con module /boot/L4Linux/run module /boot/L4Linux/loader --fprov=BMODFS run linux26.cfg module /boot/L4Linux/bmodfs module /boot/L4Linux/vmlinuz module /boot/L4Linux/drops.rd module /boot/L4Linux/linux26.cfg module /boot/L4Linux/libloader.s.so module /boot/L4Linux/libld-l4.s.so vbeset 0x117 The next one is what I got from the web. title L4Linux26/Fiasco+dope kernel /boot/L4Linux/bootstrap modaddr 0x06000000 module /boot/L4Linux/fiasco -nokdb -serial_esc module /boot/L4Linux/sigma0 module /boot/L4Linux/roottask task modname "bmodfs" attached 6 modules module /boot/L4Linux/names module /boot/L4Linux/log module /boot/L4Linux/dm_phys --isa=0x00800000 module /boot/L4Linux/simple_ts -t 300 module /boot/L4Linux/rtc module /boot/L4Linux/l4io #module /boot/L4Linux/l4dope module /boot/L4Linux/con module /boot/L4Linux/bmodfs module /boot/L4Linux/linux26.cfg module /boot/L4Linux/libloader.s.so module /boot/L4Linux/libld-l4.s.so #module /boot/L4Linux/proxygon module /boot/L4Linux/run module /boot/L4Linux/vmlinuz module /boot/L4Linux/drops.rd module /boot/L4Linux/loader --fprov=BMODFS run linux26.cfg vbeset 0x117 Compare the two, first I find my own has a events module more and some options about events, then I add these to the one I got from the web, but it runs ok without any problem. Then I changed the last lines' sequence and my own menu.lst works. Maybe that's the problem, but I'm not very sure. Another thing puzzled me was that when I entered in the l4con and in the command line state, I wanted to quit from the l4con and input Q, then the messge is "input 'y' to quit", I input 'y', but it's not responding, when I input 'z', it says OK, what does this mean?? [View Less]

2 1

problem of load file in proxygon
by Ding ying 28 Jan '08

28 Jan '08

Hello,everybody: These days I struggle with starting two l4linux on L4/Fiasco.And I have started a l4linux on hard disk and a proxygon window,then I want to load the other l4linux26.cfg file in proxygon to start the other l4linux,but it always indicated following error in proxygon <cmd>: l Load application:(nd) /tftpboot/ding/linux26-2nd run: command not found:(nd) /tftpboot/linux26-2nd I have configured the tftpserver on my system as the wiki guiding and through the … [View More]

2 1

Re: menu.lst for running flips in L4
by Björn Döbel 28 Jan '08

28 Jan '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, | Ok now, finally I managed to get the MAC address. My question is what's the | module that I need to add to my menu.lst in order to get the IP address? Is | it flips or flips-ore? depends on whether you want to use FLIPS with builtin drivers or with the ORe driver. I recommend running flips-ore along with ORe. Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.… [View More]

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers January 2008