The ultimate HOW-TO

[ComputerScienceStudent]

For completition I have to say that I use these:
------------------------------------------------------------------------------------
Prebuilt binaries of Fiasco, L4Env and L4Linux 2.6
We also provide prebuilt binaries for IA-32/i586 and Fiasco ABI version v2. 
The structure of the unpacked directory tree looks like this:

build/l4/bin/x86_586/l4v2/
    This directory contains the binaries of the supported and translated
L4Env services. 
build/fiasco_ia32/
    This directory contains the Fiasco binary. 
build/l4/lib/x86_586/, build/l4/lib/x86_586/l4v2/
    These directories contain L4Env libraries. 
build/linux_drv/
    L4Linux compiled with device drivers. 
build/linux/
    L4Linux compiled without device drivers. 
------------------------------------------------------------------------------------
Components in the snapshot
Main components

    fiasco 
    l4linux 
    dice 

L4Env

    bootstrap 
    crtx 
    cxx 
    dde 
    dde_linux 
    dde_linux26 
    demangle 
    dm_generic 
    dm_mem 
    dm_phys 
    events 
    generic_fprov 
    generic_io 
    generic_ts 
    input 
    ipcmon 
    ipreg 
    l4env 
    l4io 
    l4rm 
    l4sys 
    l4util 
    libsigma0 
    libc_backends 
    libc_backends_l4env 
    libc_support 
    linux-24-headers 
    linux-26-headers 
    ldso 
    loader 
    lock 
    log 
    lxfuxlibc 
    names 
    omega0 
    ore 
    roottask 
    rtc 
    semaphore 
    serial 
    sigma0 
    simple_ts 
    slab 
    task 
    thread 
    uclibc 
    uclibc_r 
    uclibc++ 

EMSCB extra packages

    dmon 
    dope 
    generic_blk 
    l4con 
    l4ide 
    l4vfs 
    pci 
    proxygon 
    x86emu 
-----------------------------------------------------------------------------------

..in a while I try the option earlyprintk=keep that you said me..
-- 
View this message in context: http://www.nabble.com/The-ultimate-HOW-TO-tf4192072.html#a12631925
Sent from the L4 mailing list archive at Nabble.com.