l4-hackers February 2007

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

13 participants
11 discussions

Problem booting l4linux
by Eduard Benes 28 Feb '07

28 Feb '07

Hi all, I'm newbie in this area, and I would like to ask for help with some problems I run into (hope this is the right place). I've finally build l4linux following instructions in the "L4/Fiasco/L4Linux Kickstart". (please let me know if there is better document to start with) dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf. I had some problem finding out the right configuration of the l4linux-2.6.19-l4 kernel (could someone provide example of the .conf file). Right now I'm trying to run it on real hw (How to make it run under qemu?) but when I try to boot DOpE using patched grub, it hangs when (at least I assume) trying to enter graphic mode. The screen shows this: [VESA 2.0 info @ 0x75b5000, 0x2ff bytes] boot <blank> I've tried the L4Linux demo CD, but with the same result. Tried to boot into DOpE or console. I suspect that video card might not be supported. But during many attempts, once the DOpE environment flashed for a second (before doing the restart routine accidentally) and that really surprise for me. The graphical user interface is not necessary, but I don't know yet how to run L4Linux in console. I'm able to get into kernel debugger, when I boot the L4Linux by remote serial console variant of grub menu.lst entries (based on the kickstart document mentioned above). In the kernel debugger mode was logged one error: [B.0] semaphore/lib/src/semaphore.c:500:l4semaphore_init(): Error: Missing 'deceit_bit_disables_switch' kernel feature! Startup: semaphore lib initialization failed (-1)! It is probably not related to the problem with video card, but might show some mistakes in my l4linux-2.6 kernel configuration. Here is my PCI device list: $ lspci 00:00.0 Host bridge: ATI Technologies Inc Radeon 9100 IGP Host Bridge (rev 02) 00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP AGP Bridge 00:13.0 USB Controller: ATI Technologies Inc OHCI USB Controller #1 (rev 01) 00:13.1 USB Controller: ATI Technologies Inc OHCI USB Controller #2 (rev 01) 00:14.0 SMBus: ATI Technologies Inc ATI SMBus (rev 16) 00:14.1 IDE interface: ATI Technologies Inc ATI Dual Channel Bus Master PCI IDE Controller 00:14.3 ISA bridge: ATI Technologies Inc Unknown device 434c 00:14.4 PCI bridge: ATI Technologies Inc Unknown device 4342 00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller 00:14.6 Modem: ATI Technologies Inc IXP AC'97 Modem (rev 01) 01:05.0 VGA compatible controller: ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP] 02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) 02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01) 02:07.0 USB Controller: NEC Corporation USB (rev 43) 02:07.1 USB Controller: NEC Corporation USB (rev 43) 02:07.2 USB Controller: NEC Corporation USB 2.0 (rev 04) My final goal is to compare performance of L4Linux and native Linux on real hw. I will appreciate any suggestions or study literature on this topic. Other questions I would like to ask: What is the right way to boot from serial console? How can be achieved networking under L4Linux? Regards, Eduard Benes

2 1

RE: Learning and Hacking L4 - My Bookshelf
by Stitt, Michael (AGRE) 28 Feb '07

28 Feb '07

Hi Jeff, Being in a similar boat, I don't have a good answer for you. But here's a copy (in semi-alphabetical order) of my L4 bookshelf and links to the other bookshelves I know about. Maybe you've found these already. -Hope this helps -Mike ++++L4 - My Bookshelves L4 eXperimental Kernel Reference Manual - (Karlsruhe) - Version X.2, Revision 5 - June 4 2004 http://l4ka.org/projects/pistachio/l4-x2-r5.pdf L4 User Manual - NICTA L4-embedded API - Ihor Kuz - Document Version 1.11 of October 5, 2005 http://www.ertos.nicta.com.au/software/kenge/pistachio/latest/userman.pdf L4Ka::Pistachio PowerPC Implementation Revision: 1.9 - Joshua LeVasseur - Karlsruhe http://l4ka.org/projects/pistachio/powerpc/ppc.pdf NICTA L4-embedded Kernel Reference Manual Version NICTA N1, Revision 5 http://www.ertos.nicta.com.au/software/kenge/pistachio/latest/refman.pdf On Micro-Kernel Contruction - Jochen Liedke - Karlsruhe - 15th ACM Symposium on Operating System Principles (SOSP) December 3-6, Copper Mountain Resort, Colorado http://www.l4ka.org/publications/1995/ukernel-construction.pdf Real-Time Programming and L4 Microkernels - Sergio Ruocco - NICTA - UNSW - 2007 http://www.ertos.nicta.com.au/publications/papers/Ruocco_06.abstract.pml Towards Real Microkernels - Jochen Liedke - Karlsruhe - September 1996/Vol. 39, No. 9 Communications of the ACM http://i30www.ira.uka.de/research/documents/l4ka/towards-ukernels.pdf ++++L4 - Other Bookshelves Dresden L4 Developer's Bibliography http://os.inf.tu-dresden.de/L4/bib.html Karlsruhe L4Ka Publications - OR - Karlsruhe System Architecture Group L4ka Publications http://www.l4ka.org/publications/ - OR - http://i30www.ira.uka.de/research/publications/l4ka/index.php?lid=en NICTA ERTOS Publications http://www.ertos.nicta.com.au/publications/ Teaching material from University of Karlsruhe http://i30www.ira.uka.de/teaching/courses/lecture.php?courseid=130 Teaching material from University of New South Wales http://www.cse.unsw.edu.au/~cs9242/06/lectures/ -----Original Message----- From: l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] On Behalf Of Jeff Douglas Sent: Tuesday, February 27, 2007 11:29 AM To: l4-hackers(a)os.inf.tu-dresden.de Subject: Learning and Hacking L4 Hi Coly, I've read through the X.2 spec and some of the other papers that looked like they might be useful. Unfortunately, they are not really helpful to me. Or, perhaps it is better to say that they don't seem to paint a full picture. What I think would really be helpful is the L4 System Programmer's Manual. I've waited for it to materialize for years now, but it still hasn't appeared. Do you have any particular papers to suggest? Does you know if/when the System Programmer's Manual will be released? Regards, JD >Jeff: >hi, do you read some papers for L4 ? Maybe you can start from reading >these papers. > >Coly > >在 2007-02-27二的 22:36 +0900，Jeff Douglas写道： > Greetings, > > I have had some interest in os development and theory for quite some > time now, and a particular interest in L4. I'm a newbie, but I've read > through a lot, and have done some os programming for fun in the past. > > My question is: what is your advice on learning and hacking L4? > > I've read through quite a bit of the documentation, but reading > through specs does not seem like a good way to really understand; it > seems like too much to digest at once. And of course, the purpose of a > specification is to specify, not explain. I've browsed through source > code, but that is even worse. > > I'm sorry if my question is overly broad, but I'd appreciate any > advice that anyone can spare. > > Regards, > JD > > _______________________________________________ > l4-hackers mailing list > l4-hackers at os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ______________________________________________________________________ CAUTION: This message was sent via the Public Internet and its authenticity cannot be guaranteed. ______________________________________________________ ************************************************ The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ************************************************

3 2

Re: Problem booting l4linux
by chenggh 28 Feb '07

28 Feb '07

On Wednesday 28 February 2007 11:12, Eduard Benes wrote: > Hi all, > > I'm newbie in this area, and I would like to ask for help with some > problems I run into (hope this is the right place). I've finally build > l4linux following instructions in the "L4/Fiasco/L4Linux Kickstart". > (please let me know if there is better document to start with) > dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf. We have tested this document many times and some Linux newbie used this document to build the L4Linux very successfully. And please pay attention that this document is made in the case of kernel 2.6.17. Maybe in the kernel 2.6.19 there are some problems, too. > I had some problem finding out the right configuration of the > l4linux-2.6.19-l4 kernel (could someone provide example of the .conf file). > Right now I'm trying to run it on real hw (How to make it run under qemu?) > but when I try to boot DOpE using patched grub, it hangs when (at least I > assume) trying to enter graphic mode. The screen shows this: If you use L4Linux or Fiasco the first thing is to study how to use serial console to debug the Fiasco especially in the graphical mode you don't see anything important in the screen. Some booting error messages could only be output by the serial console. > I've tried the L4Linux demo CD, but with the same result. Tried to boot > into DOpE or console. I suspect that video card might not be supported. But > during many attempts, once the DOpE environment flashed for a second > (before doing the restart routine accidentally) and that really surprise > for me. The graphical user interface is not necessary, but I don't know yet > how to run L4Linux in console. I'm able to get into kernel debugger, when I > boot the L4Linux by remote serial console variant of grub menu.lst entries > (based on the kickstart document mentioned above). In the kernel debugger > mode was logged one error: > [B.0] semaphore/lib/src/semaphore.c:500:l4semaphore_init(): > Error: Missing 'deceit_bit_disables_switch' kernel feature! > Startup: semaphore lib initialization failed (-1)! > It is probably not related to the problem with video card, but might show > some mistakes in my l4linux-2.6 kernel configuration. > If you still have some problems about compiling or booting, please download this tar ball (http://dslab.lzu.edu.cn/~chenggh/doc/L4.tar). I have tested this tar ball many times successfully and if you use this directory and do as the kickstart says. I promise you could be successful. In this letter there are 2 attachments: one is 2.4.17 configuration file for booting from serial console and another is 2.4.17 configuration file for booting from Dope. > My final goal is to compare performance of L4Linux and native Linux on real > hw. I will appreciate any suggestions or study literature on this topic. I have done some similar work as you want to do and if you want know something about my paper and data please access my home page (dslab.lzu.edu.cn/~chenggh). > Other questions I would like to ask: > What is the right way to boot from serial console? Please review my kickstart and some configuration file. > How can be achieved networking under L4Linux? In my benchmark about performance comparasion between L4Linux and Linux I use L4Linux network (It is same as you do in Linux). But if you want to use Fiasco network there is a module ORe (the Oshkosh Resurrection) you could try. But I think this module only show us the Fiasco supports network, too and you don't do anything meaningful. Thank you. I hope you could modify my kickstart and give the new version of this kickstart. Thank you. cheng

1 0

Learning and Hacking L4
by Jeff Douglas 27 Feb '07

27 Feb '07

Hi Coly, I've read through the X.2 spec and some of the other papers that looked like they might be useful. Unfortunately, they are not really helpful to me. Or, perhaps it is better to say that they don't seem to paint a full picture. What I think would really be helpful is the L4 System Programmer's Manual. I've waited for it to materialize for years now, but it still hasn't appeared. Do you have any particular papers to suggest? Does you know if/when the System Programmer's Manual will be released? Regards, JD >Jeff: >hi, do you read some papers for L4 ? Maybe you can start from reading >these papers. > >Coly > >在 2007-02-27二的 22:36 +0900，Jeff Douglas写道： > Greetings, > > I have had some interest in os development and theory for quite some > time now, and a particular interest in L4. I'm a newbie, but I've read > through a lot, and have done some os programming for fun in the past. > > My question is: what is your advice on learning and hacking L4? > > I've read through quite a bit of the documentation, but reading > through specs does not seem like a good way to really understand; it > seems like too much to digest at once. And of course, the purpose of a > specification is to specify, not explain. I've browsed through source > code, but that is even worse. > > I'm sorry if my question is overly broad, but I'd appreciate any > advice that anyone can spare. > > Regards, > JD > > _______________________________________________ > l4-hackers mailing list > l4-hackers at os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

3 2

Learning and Hacking L4
by Jeff Douglas 27 Feb '07

27 Feb '07

Greetings, I have had some interest in os development and theory for quite some time now, and a particular interest in L4. I'm a newbie, but I've read through a lot, and have done some os programming for fun in the past. My question is: what is your advice on learning and hacking L4? I've read through quite a bit of the documentation, but reading through specs does not seem like a good way to really understand; it seems like too much to digest at once. And of course, the purpose of a specification is to specify, not explain. I've browsed through source code, but that is even worse. I'm sorry if my question is overly broad, but I'd appreciate any advice that anyone can spare. Regards, JD

2 1

IPC problem
by Michael Scheibel 16 Feb '07

16 Feb '07

Hello L4 hackers, we've encountered a problem with an IPC transmission based on DICE stubs generated from the following interface definition: UInt32 process( [in, size_is(bufferALen), max_is(MAX_BUFFER_SIZE)] UInt8* bufferA, [in] UInt32 bufferALen, [in, size_is(bufferBLen), max_is(MAX_BUFFER_SIZE)] UInt8* bufferB , [in] UInt32 bufferBLen, [out, size_is(*bufferCLen), max_is(MAX_BUFFER_SIZE)] UInt8** bufferC, [out] UInt32* bufferCLen); UInt8 is defined as unsigned char, UInt32 is defined as unsigned long, MAX_BUFFER_SIZE is 1500. We are using dice version 3.1.0 with the command line options -fforce-corba-alloc -nostdinc -P-DL4API_l4v2 and the latest OTC snapshot. In this configuration bufferB is not transmitted correctly but is received as corrupt data on the server side (which is an L4Linux application). Is there anything wrong with our interface definition? Any hints appreciated! Michael -- Sirrix AG security technologies - http://www.sirrix.com Michael Scheibel eMail: m.scheibel(a)sirrix.com Tel +49(234) 610 071-124 Public key on demand. Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 4

small address-space can not be used in em64t mode ?
by coly 14 Feb '07

14 Feb '07

Hi, The transparently flexing user address space method which is called as "small address-space" uses segment to implement the protection for small address sapce. But in em64t or amd64 mode, there is not segment (except FS,GS) exists. So it seems the small address-space method can not be used under 64bit mode. Isn't it ? Thanks in advance. Coly

2 1

Booting L4Linux on Fiasco-UX fails with kernel panic
by Michael Kasper 14 Feb '07

14 Feb '07

Hello L4-Hackers, I try to become familiar with L4Linux on top of Fiasco-UX. Therefor, I've rebuilt the sources as described online. But booting L4Linux with the example drops-rd.rd ramdisk fails with kernel panic. Shortly after the ramdisk is loaded, the boot process halts with the following message: Kernel panic - not syncing: No init found. Try passing init= option to kernel. panic: going to sleep forever, bye Has anyone a solution for this? Is the ramdisk not accessible by the L4Linux kernel, or do I need explicitly specify an init parameter? Thanks and kind regards, Michael ################################################# Fiasco-UX on Linux 2.6.18-gentoo-r6 (i686) Native Syscall Map: 0x600 Mapped 256 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00099364 [/base/drops/l4/build/bin/x86_586/l4v2/sigma0] Loading Module 0x00120000-0x002b29e4 [/base/drops/l4/build/bin/x86_586/l4v2/roottask] Copying Module 0x0ea5d000-0x0ea847ff [/base/drops/l4/kernel/fiasco/build/Symbols] Copying Module 0x0ea24000-0x0ea5cedc [/base/drops/l4/kernel/fiasco/build/Lines] Copying Module 0x0e9e4000-0x0ea2347e [/base/drops/l4/build/bin/x86_586/l4v2/names] Copying Module 0x0e9a7000-0x0e9e3dc8 [/base/drops/l4/build/bin/x86_586/l4v2/log] Copying Module 0x0e921000-0x0e9a63c7 [/base/drops/l4/build/bin/x86_586/l4v2/dm_phys] Copying Module 0x0e8d6000-0x0e92068d [/base/drops/l4/build/bin/x86_586/l4v2/simple_ts] Copying Module 0x0e822000-0x0e8d5804 [/base/drops/l4/build/bin/x86_586/l4v2/fuxfprov] Copying Module 0x0e7f0000-0x0e821f37 [/base/drops/l4/build/bin/x86_586/l4v2/rtc-ux] Copying Module 0x0e71e000-0x0e7ef395 [/base/drops/l4/build/bin/x86_586/l4v2/loader] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 3.4.6 for Intel Pentium CPU: GenuineIntel (6:F:6:0) Model: Core 2 (Merom) at 2394 MHz 128 Entry I TLB (4K pages) 272 Entry D TLB (4K pages) 48 Entry D TLB (4M pages) 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 4096 KB L2 U Cache (16-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ ea99000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Found Fiasco-UX. Command line found: "/base/drops/l4/build/bin/x86_586/l4v2/roottask -symbols -lines" 261120kB ( 255MB) total RAM (reported by bootloader) 235040kB ( 230MB) received RAM from Sigma0 5488kB ( 6MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 A B C D E F ] Roottask: Loading 7 modules. #05: loading "/base/drops/l4/build/bin/x86_586/l4v2/names " from [0e9e4000-0ea2347e] to [002d0000-002d5f6a][002d6000-002e2000] entry at 0000d088 via trampoline page code #06: loading "/base/drops/l4/build/bin/x86_586/l4v2/log" from [0e9a7000-0e9e3dc8] to [00400000-004064ca][00407000-004398b0] entry at 0000e084 via trampoline page code #07: loading "/base/drops/l4/build/bin/x86_586/l4v2/dm_phys " from [0e921000-0e9a63c7] to [01500000-0150e50a][0150f000-01519000] entry at 0000f088 via trampoline page code #08: loading "/base/drops/l4/build/bin/x86_586/l4v2/simple_ts " from [0e8d6000-0e92068d] to [01400000-014080ea][01409000-0141b070] entry at 0001008c via trampoline page code #09: loading "/base/drops/l4/build/bin/x86_586/l4v2/fuxfprov" from [0e822000-0e8d5804] to [00500000-0051ec6c][0051f000-00553000] entry at 00011088 via trampoline page code #0a: loading "/base/drops/l4/build/bin/x86_586/l4v2/rtc-ux" from [0e7f0000-0e821f37] to [01080000-01084040][01085000-0108a000] entry at 00012088 via trampoline page code #0b: loading "/base/drops/l4/build/bin/x86_586/l4v2/loader /base/drops/l4/cfg/l4linux26.ux" from [0e71e000-0e7ef395] to [01300000-01320642][01321000-0134c000] entry at 000130a8 via trampoline page code simplets| Configured for 64 tasks. loader | Can't map tbuf status page fuxfprov| File provider started, registered as 9.02 fuxfprov| open "/base/drops/l4/cfg/l4linux26.ux" by B.02 loader | sleeping for 2000 ms fuxfprov| open "/base/drops/l4linux-2.6/vmlinuz26.ux" by B.02 loader | vmlinuz26.ux: Starting application using libld-l4.s.so loader | vmlinuz26.ux,#c: Loading binary fuxfprov| open "/base/drops/l4/build/bin/x86_586/l4v2/libld-l4.s.so" by B.02 loader | vmlinuz26.ux,#c: Loading ldso loader | Capability support not supported. loader | vmlinuz26.ux,#c: Starting libld-l4.s.so at 00013890 via 0000cf00 fuxfprov| open "./libloader.s.so" by C.00 fuxfprov| Can't open "./libloader.s.so": -2 fuxfprov| open "/base/drops/l4/build/bin/x86_586/l4v2/./libloader.s.so" by C.00 fuxfprov| open "/base/drops/l4linux-2.6/vmlinuz26.ux" by C.00 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.19-l4 (root@localhost) (gcc version 3.4.6 (Gentoo 3 l4lx : .4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #30 Wed Feb 14 15:53:39 Local tim l4lx : e zone must be set--see zic man l4lx | Binary name: /base/drops/l4linux-2.6/vmlinuz26.ux l4lx | Kernel command line (7 args): mem=128M root=1:0 load_ramdisk=1 ramdis l4lx : k_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de l4lx | Image: 00400000 - 0054e000 [1336 KiB]. l4lx | Areas: Text: 00400000 - 004cf000 [828kB] (a bit longer) l4lx | Data: 004cf000 - 004eb63c [113kB] l4lx | Initdata: 004ee000 - 00503000 [84kB] l4lx | BSS: 00504000 - 0054cd50 [291kB] l4lx | l4lx_thread_create: Created thread 0c.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0c.04 (server) l4lx | main thread will be 0c.04 l4lx | l4env_register_pointer_section: addr = 004cf000 size = 520192 l4lx | sec-w-init: virt: 0x004cf000 to 0x0054dfff [508 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 520192 Bytes l4lx | sec-w-init: 1: Phys: 0x0127d000 to 0x012f6000, Size: 495616 l4lx | sec-w-init: 2: Phys: 0x01356000 to 0x0135c000, Size: 24576 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 128MB l4lx | Main memory: virt: 0x00800000 to 0x087fffff [131072 KiB] l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes l4lx | Main memory: 1: Phys: 0x01800000 to 0x09800000, Size: 134217728 l4lx | Filling lower ptabs... l4lx | Done (1582 entries). l4lx | l4lx_thread_create: Created thread 0c.05 (timer.i0) Linux version 2.6.19-l4 (root@localhost) (gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #30 Wed Feb 14 15:53:39 Local time zone must be set--see zic man dm_phys: 0000000000800000 - 0000000008800000 [131072 KiB] (usable) 128MB memory available. Zone PFN ranges: DMA 0 -> 512 Normal 512 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 Allocating PCI resources starting at 10000000 (gap: 08800000:f7800000) Detected 2394.000 MHz processor. Built 1 zonelists. Total pages: 34544 Kernel command line: mem=128M root=1:0 load_ramdisk=1 ramdisk_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de Initializing CPU#0 PID hash table entries: 1024 (order: 10, 4096 bytes) l4lx_irq_timer_startup(0) timer_irq_thread: Starting timer IRQ thread. l4ser_init_ports l4ser: vkey_irq not set - input disabled! Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 129620k/139264k available (729k kernel code, 1300k reserved, 211k data, 84k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0x10000000 - 0x18000000 ( 128 MB) lowmem : 0x00000000 - 0x08800000 ( 136 MB) .init : 0x004ee000 - 0x00503000 ( 84 kB) .data : 0x004b670c - 0x004eb63c ( 211 kB) .text : 0x00400000 - 0x004b670c ( 729 kB) Calibrating delay using timer specific routine.. 4680.80 BogoMIPS (lpj=23404042) Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K Compat vDSO mapped to 0040e000. CPU: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz stepping 06 Setting up standard PCI resources fuse init (API version 7.7) L4 serial driver l4ser_init_ports l4ser: vkey_irq not set - input disabled! ttyLv0 at MMIO 0x1 (irq = 0) is a L4 Kernel panic - not syncing: No init found. Try passing init= option to kernel. panic: going to sleep forever, bye l4lx | panic: going to sleep forever, bye Time: tsc clocksource has been installed. ############################################### # # L4Linux26.ux # modpath "/base/drops/l4linux-2.6" libpath "/base/drops/l4/build/bin/x86_586/l4v2" sleep 2 task "/base/drops/l4linux-2.6/vmlinuz26.ux" "mem=128M root=1:0 load_ramdisk=1 ramdisk_size=5659274 l4env_rd=/base/drops/drops-rd.rd panicblink=0 lang=de" allow_cli all_sects_writable priority 0xA0 ############################################### # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_OBJ_TREE="/base/drops/l4/build" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 CONFIG_L4_USERPRIV_ONLY=y CONFIG_L4_L4ENV_MEMSIZE=128 CONFIG_L4_TAMED=y # # L4 build options # CONFIG_L4_MK_CPU_X86="586" # # IRQ Handling # # CONFIG_L4_IRQ_SINGLE is not set CONFIG_L4_IRQ_OMEGA0=y # CONFIG_L4_IRQ_MULTI is not set # # Stub drivers # CONFIG_L4_EXTERNAL_RTC=y # CONFIG_L4_BLK_DRV is not set # CONFIG_L4_PDSPBLK_DRV is not set # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set CONFIG_L4_SERIAL=y CONFIG_L4_SERIAL_CONSOLE=y # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set # # Priority configuration # CONFIG_L4_PRIO_USER_PROCESS=10 CONFIG_L4_PRIO_IRQ_OFFSET=129 CONFIG_L4_PRIO_SERVER=100 # # Debugging options # CONFIG_L4_DEBUG=y CONFIG_L4_DEBUG_REGISTER_NAMES=y CONFIG_L4_DEBUG_SEGFAULTS=y CONFIG_L4_DEBUG_STATS=y # CONFIG_L4_DEBUG_IRQ_WHEELS is not set CONFIG_L4_DEBUG_TAMED_COUNT_INTERRUPT_DISABLE=y # # Monitoring options (ferret) # # CONFIG_L4_FERRET_USER is not set # CONFIG_L4_FERRET_KERNEL is not set # CONFIG_L4_FERRET_SYSCALL_COUNTER is not set # # # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_UTS_NS is not set # CONFIG_IKCONFIG is not set # CONFIG_RELAY is not set CONFIG_INITRAMFS_SOURCE="" # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set # CONFIG_HOTPLUG is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # # CONFIG_BLOCK is not set # # Processor type and features # # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set CONFIG_M586=y # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HPET_TIMER is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set CONFIG_VM86=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is not set # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set CONFIG_COMPAT_VDSO=y # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # # CONFIG_PCI is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_MISC=m # # Networking # # CONFIG_NET is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_SYS_HYPERVISOR is not set # # Connector - unified userspace <-> kernelspace linker # # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # # Misc devices # # CONFIG_TIFM_CORE is not set # # SCSI device support # # CONFIG_SCSI_NETLINK is not set # # Serial ATA (prod) and Parallel ATA (experimental) drivers # # # Fusion MPT device support # # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # # I2O device support # # # ISDN subsystem # # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # # CONFIG_INPUT is not set # # Hardware I/O ports # # CONFIG_SERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # # CONFIG_VT is not set # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set # # I2C support # # CONFIG_I2C is not set # # SPI support # # CONFIG_SPI is not set # CONFIG_SPI_MASTER is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # # CONFIG_HWMON is not set # CONFIG_HWMON_VID is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # # Graphics support # # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # # CONFIG_USB_ARCH_HAS_HCD is not set # CONFIG_USB_ARCH_HAS_OHCI is not set # CONFIG_USB_ARCH_HAS_EHCI is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # LED devices # # CONFIG_NEW_LEDS is not set # # LED drivers # # # LED Triggers # # # InfiniBand support # # # EDAC - error detection and reporting (RAS) (EXPERIMENTAL) # # CONFIG_EDAC is not set # # Real Time Clock # # CONFIG_RTC_CLASS is not set # # DMA Engine support # # CONFIG_DMA_ENGINE is not set # # DMA Clients # # # DMA Devices # # # File systems # CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y CONFIG_FUSE_FS=y # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_CONFIGFS_FS is not set # # Miscellaneous filesystems # # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_MAGIC_SYSRQ=y # CONFIG_UNUSED_SYMBOLS is not set # CONFIG_DEBUG_KERNEL is not set CONFIG_LOG_BUF_SHIFT=14 # CONFIG_DEBUG_BUGVERBOSE is not set # CONFIG_DEBUG_FS is not set # CONFIG_UNWIND_INFO is not set # CONFIG_HEADERS_CHECK is not set CONFIG_EARLY_PRINTK=y # CONFIG_DOUBLEFAULT is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_MANAGER=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set # CONFIG_CRC16 is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_PLIST=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y

2 1

large memory model kernel
by David Shifflett 12 Feb '07

12 Feb '07

Hi, I am looking for a development and run-time environment for an experimental kernel. I want to run large memory model (multiple code and data segments). Can L4 / Fiasco support a segmented architecture? Can it support large memory model code? What file formats (ELF, COFF, LE/LX) does it support? What compiler/linker might work? (I am looking at Open WATCOM) Thanks in advance, dave

2 1

Problem compiling dice
by thbach＠students.uni-mainz.de 12 Feb '07

12 Feb '07

Hi, trying to compile the recent cvs-source I got the following error (both, with bison and byacc), while compiling dice: mv -f .deps/IncludeStatement.Tpo .deps/IncludeStatement.Po g++ -DHAVE_CONFIG_H -I. -I.. -D__USER__="\"knoppix@`hostname`\"" -D__L4DIR__="\"`pwd`/../../..\"" -D__DICEINCDIR__="\"/home/drops/include\"" -Wall -I../src -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -MT Exception.o -MD -MP -MF .deps/Exception.Tpo -c -o Exception.o Exception.cpp mv -f .deps/Exception.Tpo .deps/Exception.Po g++ -DHAVE_CONFIG_H -I. -I.. -D__USER__="\"knoppix@`hostname`\"" -D__L4DIR__="\"`pwd`/../../..\"" -D__DICEINCDIR__="\"/home/drops/include\"" -Wall -I../src -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -MT Dependency.o -MD -MP -MF .deps/Dependency.Tpo -c -o Dependency.o Dependency.cpp mv -f .deps/Dependency.Tpo .deps/Dependency.Po g++ -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith -Wshadow -Wwrite-strings -g -O2 -export-dynamic -o dice main.o Compiler.o CParser.o File.o Object.o Visitor.o version.o CCParser.o CCXXParser.o CDCEParser.o CCORBAParser.o CPreProcess.o IncludeStatement.o Exception.o Dependency.o -L../src/be/l4/v2 -lv2 -L../src/be/l4/v2/amd64 -lv2amd64 -L../src/be/l4/v2/ia32 -lv2ia32 -L../src/be/l4/x0 -lx0 -L../src/be/l4/v4 -lv4 -L../src/be/l4/v4/ia32 -lv4ia32 -L../src/be/l4 -ll4 -L../src/be/sock -lsock -L../src/be/cdr -lcdr -L../src/be -lbe -L../src/parser/dce -ldce -L../src/parser/corba -lcorba -L../src/parser/inc -linc -L../src/parser/gcc-c -lgcc_c -L../src/parser/gcc-cxx -lgcc_cxx -L../src/fe -lfe -lstdc++ -ldl collect2: ld returned 1 exit status make[6]: *** [dice] Fehler 1 make[6]: Leaving directory `/home/knoppix/l4/l4/tool/dice/src' make[5]: *** [all-recursive] Fehler 1 make[5]: Leaving directory `/home/knoppix/l4/l4/tool/dice/src' make[4]: *** [all-recursive] Fehler 1 make[4]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[3]: *** [all] Fehler 2 make[3]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[2]: *** [all] Fehler 2 make[2]: Leaving directory `/home/knoppix/l4/l4/tool/dice' make[1]: *** [dice] Fehler 2 make[1]: Leaving directory `/home/knoppix/l4/l4/tool' make: *** [tool] Fehler 2 There was allready someone else having this problem in the mailing-list... Any suggestions? Greets, Vincent

2 4

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 February 2007