l4-hackers March 2014

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

22 participants
31 discussions

In Freescale i.MX6q_sabre_sd,The problem booting Helloworld + L4 + Fiasco
by taeung 17 Mar '14

17 Mar '14

Hello, L4 hackers. I have one question. please help me.. I have failed booting 'L4 Linux + L4 + Fiasco' on my board(Freescale i.MX6 Quad SABRE SD : Cortex-A9 , ARMv7) So, i'm try to boot 'Helloword + L4 + Fiasco' on my board Such as.. |$ svn cathttp://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - inithttp://svn.tudos.org/repos/oc/tudos fiasco l4re | 1. L4 Re : configure and build (Success) |||==========================================================================| $ mkdir -p /path/to/obj/tudos |$ make O=/path/to/obj/tudos oldconfig $ make O=/path/to/obj/tudos -j2| |========================================================================== | |2. Fiasco : configure and build (Success)| || |========================================================================== $ cd /somedir/tudos/src/kernel/fiasco $ make BUILDDIR=/path/to/obj/fiasco $ cd /path/to/obj/fiasco $ make menuconfig $ make ========================================================================== 3. But,when i try to 'make uimage' or 'make qemu', error is happened. such as.. ========================================================================== root@taeung-MS-7798:/path/to/obj2/tudos# make uimage E=hello-cfg MODULE_SEARCH_PATH=/path/to/obj2/fiasco/ make[1]: Entering directory `/home/taeung/Hello_test_l4/src/l4' =========== Updating RAM_BASE for platform imx6 to 0x10000000 ========= ... Regenerating RAM_BASE settings Library dependencies missing: libc_minimal cxx_util cxx_io cxx_base cxx_io_kdebug l4sys-direct l4sys in directory '/home/taeung/Hello_test_l4/src/l4/pkg/sigma0/server/src'; aborting. /home/taeung/Hello_test_l4/src/l4/mk/binary.inc:348: *** Cflags dependencies missing: libc_minimal cxx_util cxx_io cxx_base cxx_io_kdebug l4sys-direct l4sys in directory '/home/taeung/Hello_test_l4/src/l4/pkg/sigma0/server/src'; aborting.. Stop. make[2]: *** [/path/to/obj2/tudos/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f] Error 2 make[1]: *** [check_and_adjust_ram_base] Error 2 ========================================================================== |<< My Question >> Although i search of '|Library dependencies missing: libc_minimal cxx_util cxx_io cxx_base cxx_io_kdebug l4sys-direct l4sys|' in google.com, i could'nt get information about this error. I don't know why the problem is happened updating |'RAM_BASE for platform imx6 to 0x10000000'. | || Please any help.. /Regards, Taeung Song | Student of Computer Engineering Hansung University./

2 2

L4Linux + L4re + Fiasco to boot in Freescale i.MX6q_sabre_sd
by taeung 17 Mar '14

17 Mar '14

Hello L4 hackers. I have two question (My question 1, 2 ). please help me. I'm trying to boot 'L4Linux + L4re + Fiasco' in Freescale i.MX6 Quad SABRE SD board (Cortex-A8, ARMv7-A). Such as.. 0. Get Source and install required package. |$ cd /somedir/tudos $ svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos fiasco l4re l4linux_requirements| 1. L4 Re : configure and build (Success) |||==========================================================================| $ mkdir -p /path/to/obj/tudos |$ make O=/path/to/obj/tudos oldconfig $ make O=/path/to/obj/tudos -j2| |==========================================================================| 2. Fiasco : configure and build (Success) |==========================================================================| ||$ cd /somedir/tudos/src/kernel/fiasco |$ make BUILDDIR=/path/to/obj/fiasco $ cd /path/to/obj/fiasco $ make menuconfig $ make| |==========================================================================| 3. L4 linux : configure and build. (Failure) (Here, i have trouble to build l4 linux after configure according to my board ) |==========================================================================| |$ cd /somedir/tudos $ svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux $ cd l4linux $ mkdir /path/to/obj/l4linux $ make L4ARCH=arm CROSS_COMPILE=arm-linux- O=/path/to/obj/l4linux arm_defconfig # In the menu, in "L4Linux configuration", set "L4 tree build directory" to /path/to/obj/tudos $ make L4ARCH=arm CROSS_COMPILE=arm-linux- O=/path/to/obj/l4linux menuconfig ||==========================================================================| To configure according to my board(Freescale i.MX6q_sabre_sd), I was able to choice two kinds. <The first > |System type -> ARM system type (L4 Linux) Build type (Use ARMv7) | <Result of the first > 1) Sucess build L4 linux and i got 'vmlinuz.arm' 2) 'make uImage' according to module.list |========================================================================== entry L4Linux_xs_2 kernel fiasco -nokdb roottask moe rom/l4linux.cfg module l4linux.cfg module l4re module ned module vmlinuz.arm module ramdisk-arm.rd| |==========================================================================| 3) i make SD Card bootable by u-boot.bin and bootstrap.uImage 4) Booting L4Linux + L4re + Fiasco in Freescale i.MX6q_sabre_sd But, i have problem to boot it. =========================================================================== U-Boot 2009.08 (Aug 16 2013 - 12:04:20) CPU: Freescale i.MX6 family TO1.2 at 792 MHz Thermal sensor with ratio = 180 Temperature: 44 C, calibration data 0x5764ba7d mx6q pll1: 792MHz mx6q pll2: 528MHz mx6q pll3: 480MHz mx6q pll8: 50MHz ipg clock : 66000000Hz ipg per clock : 66000000Hz uart clock : 80000000Hz cspi clock : 60000000Hz ahb clock : 132000000Hz axi clock : 264000000Hz emi_slow clock: 132000000Hz ddr clock : 528000000Hz usdhc1 clock : 198000000Hz usdhc2 clock : 198000000Hz usdhc3 clock : 198000000Hz usdhc4 clock : 198000000Hz nfc clock : 24000000Hz Board: i.MX6Q-SABRESD: unknown-board Board: 0x63012 [POR ] Boot Device: SD I2C: ready DRAM: 1 GB MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3 In: serial Out: serial Err: serial i2c: I2C3 SDA is low, start i2c recovery... I2C3 Recovery success Found PFUZE100! deviceid=10,revid=11 Net: got MAC address from IIM: 00:04:9f:02:70:b5 FEC0 [PRIME] Hit any key to stop autoboot: 0 mmc2 is current device MMC read: dev # 2, block # 2048, count 17408 ... 17408 blocks read: OK ## Booting kernel from Legacy Image at 10800000 ... Image Name: L4 Image #7 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 7680000 Bytes = 7.3 MB Load Address: 11000000 Entry Point: 11000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... ========================================= <My question 1.> Why hang at 'Starting kernel ...' ? Setting environment variable and bootcmd , i have thought the setting is no problem. This kernel image is wrong? <The Second > |System type ---> ARM system type (Allow multiple platforms to be selected)| Multiple platform selection ---> ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait) Build type Freescale i.MX family Freescale i.MX support ---> i.MX6 Quad/DualLite support <Result of the second > i could not build l4 linux because.. GEN /path/to/obj/l4linux/Makefile scripts/kconfig/conf --silentoldconfig Kconfig ERROR: CONFIG_ARM_PATCH_PHYS_VIRT must not be enabled. make[1]: *** [check_linux_config] Error 1 make: *** [sub-make] Error 2 <My question 2.> Why can not build L4 linux according to this config ? and What is CONFIG_ARM_PATCH_PHYS_VIRT ? Please any help.. /Regards, Taeung Song | Student of Computer Engineering Hansung University. /

2 1

Re: Problem in Linking program
by Irvanda Kurniadi 13 Mar '14

13 Mar '14

Case closed. I found that the __assert_fail is not supported in uclibc. Then, I tried to change __assert_fail with __assert and it works. But I'm still curious about using glibc in L4re. I try to compile my program using libgcc but it also doesn't work. Can it cause any problem if I use glibc compiler than any of requires_libs using uclibc compiler? just wondering irvanda

2 1

Problem in Linking program
by Irvanda Kurniadi 12 Mar '14

12 Mar '14

Hi, I'm trying to build my program in L4/Fiasco. This program requires libtiff, MPI, and libstep library. I've ported those all libraries. But, when I built my program, I got a problem in linking program. The compilation just work fine but when entering the linking part, I got this error message: ==> Linking sobel-step ........ main-sobel-V4.cpp_processed.o: In function `main': /home/l4re-mpich/src/l4/pkg/sobel-step/server/src/main-sobel-V4.cpp_processed.c:57: undefined reference to `__assert_fail' /home/l4re-mpich/src/l4/pkg/sobel-step/server/src/main-sobel-V4.cpp_processed.c:56: undefined reference to `__assert_fail' ......... This "__assert_fail" should be available in libstep.so and I've put the LDFLAGS = -lstep on my makefile. Here is my Makefiel anyway: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. SYSTEMS = x86-l4f amd64-l4f include $(L4DIR)/mk/Makeconf ifneq ($(SYSTEM),) # check whether used gcc has the omp.h file available OMP_H_PATH := $(shell $(CC) -print-file-name=include/omp.h) ifeq ($(strip $(OMP_H_PATH)),include/omp.h) $(info [32m $(CC) does not have omp.h header file available, skipping.[0m) else TARGET = $(if $(filter 4.2 4.3 4.4 4.5 4.6 4.7,$(GCCVERSION)),sobel-step) REQUIRES_LIBS = libgomp libtiff libmpich libmpich_f77sup libstep libc libc_support_misc endif endif SRC_C = main-sobel-V4.cpp_processed.c sobel-omp-V4.cpp_processed.c pictureInterface.c util.c CFLAGS += -fopenmp -I. -g -Wall LDFLAGS += -rpath -ltiff -rpath -lstep PRIVATE_INCDIR = $(SRC_DIR) vpath %.c $(SRC_DIR) include $(L4DIR)/mk/prog.mk Previously I compiled the program and there are so much missing shared libraries and the debug message suggested to add the -rpath. I updated my LDFLAGS by adding the -rpath. Here is the error message before I add the LDFLAGS with -rpath: ==> Linking sobel-step .... ld: warning: libl4z.so, needed by /home/l4re-mpich/obj/l4/x86/lib/x86_586/l4f/libtiff.so, not found (try using -rpath or -rpath-link) ld: warning: libgfortran.so, needed by /home/l4re-mpich/obj/l4/x86/lib/x86_586/l4f/libstep.so, not found (try using -rpath or -rpath-link) ....... ld: final link failed: Bad value I'm not sure whether this is causing another problem by adding the -rpath. I mean, Is it the proper way to fix the missing shared library? Because the "__asser_fail" is supposed to be found in the libstep.so but I still got the undefined reference error message. So perhaps there are several things to wrap up this linking problem. If you by any chance find any misplace or missing configuration in my makefile or you have any idea how to fix it please let me know. Thanks Regards, Irvanda

1 0

seL4 what exactly is in the kernel
by Taylor Bioniks 11 Mar '14

11 Mar '14

Like all L4 kernels, it provides basic mechanisms which must be in the kernel for security reasons. These include low-level interrupt and exception handlers (which essentially convert these events into IPC messages to user-level handlers), a notion of address spaces into which you can map frames (basically an abstraction of page tables), a notion of kernel-scheduled (and context-switched) threads, a notion of a protection domain (capability tree) and a communication and synchronisation mechanism (IPC endpoints). Other L4 kernels have similar abstractions. Please explain what you mean by notion? Do you mean that it has code to deal with the user mode memory management and such? What is different in seL4 is that all memory management is done at user level. After booting up and allocating and initialising its static data structures (scheduling queues, the kernel stack and a few globals) the kernel sets up an initial user address space with a single thread, and hands it the rights to all remaining memory (in the form of "Untyped" capabilities). When performing an operation that requires kernel data structures (eg creating a thread requires creating a thread control block, TCB) the user has to provide these, by "retyping" some Untyped memory into a kernel object type. This makes it kernel memory (inaccessible to userland), but the owner of that memory can always revoke it (revert it to Untuped, thus nuking the kernel object). so is the single kernel stack in it's own address space or is it somehow mapped or shared with other address spaces? There's a single kernel stack, which is in use whenever kernel code executes. The terms "kernel mode" or "user mode" make no sense for data - they refer to the processor mode that is active when particular code is executing. However, the kernel stack is, of course, a kernel object, only accessible in kernel mode. While the kernel stack (like the scheduler queues) is somewhat special, in that it is allocated by the kernel at boot time, in terms of accessibility it's no different from other "kernel objects", such as PTs or TCBs, that are allocated by userland. so kernel objects are stored in this user mode kernel stack? Okay, so the kernel never actually has a stack in kernel mode, and it never allocates space for itself does this mean that the kernel does not grow? And if so does that eliminate the requirement that I've seen on X86 machines where they have 1GB for the kernel and 3GB for the user programs Final thing is I've been pointed to the university site a few times and I've been told there are slides with audio on there, however, I can never find them even after mirroring the site and looking through it. Where might I find these?

2 1

Problem when booting L4 Fiasco/Re
by Sören Jonsson 11 Mar '14

11 Mar '14

Hello, I have now successfully compiled the L4 Fiasco.OC and your runtime environment. I made the hello.iso bootable image as well, and made an attempt to run it under VMWare workstation. My problem is that it don't work. It stops during boot, with the following information: I had to provide two images, in order to capture all information. The information above "Total RAM: 255MB" disapers very fast otherwise. Is this enough information to explain what is happening, or can I provide more information using other methods? With my best regards, Sören Jonsson Sweden

2 1

seL4 what exactly is in the kernel
by Taylor Bioniks 08 Mar '14

08 Mar '14

What does the seL4 kernel actually provide in the kernel itself? I've read through documentation and it seems they just stop before they state exactly what the seL4 kernel does. So what I'd like to know is what features and components are in the kernel and what is outside of it? Does the kernel have a single kernel stack or multiple kernel stacks and is/are it/they in kernel mode or user mode? Are there any good diagrams that show how seL4 works with its user space components? Thanks in advance

2 1

Panic with l4Linux
by Ismael BARAKAT 07 Mar '14

07 Mar '14

Hello, I'm working on Fiasco, l4Re and l4Linux. I build the uImage for an arm architecture. When I boot it, I have a "panic: going to sleep forever, bye". Can someone help I don't know what caused the problem. This is the information I have on my console when I boot: L4 Bootstrapper Build: #10 Thu Mar 6 11:11:19 CET 2014, 4.7.3 Scanning up to 128 MB RAM Memory size is 128MB (80000000 - 87ffffff) RAM: 0000000080000000 - 0000000087ffffff: 131072kB Total RAM: 128MB mod07: 813f7000-816f7000: ramdisk-arm.rd mod06: 81125000-813f6480: vmlinuz.arm mod05: 81124000-81124189: l4Linux.cfg mod04: 810d1000-81123bc0: ned mod03: 810b7000-810d0458: l4re mod02: 81085000-810b6624: moe mod01: 8107b000-8108433c: sigma0 mod00: 81015000-8107a3a8: fiasco Moving up to 8 modules behind 81100000 moving module 00 { 81015000-8107a3a7 } -> { 817e2000-818473a7 } [414632] moving module 01 { 8107b000-8108433b } -> { 81848000-8185133b } [37692] moving module 02 { 81085000-810b6623 } -> { 81852000-81883623 } [202276] moving module 03 { 810b7000-810d0457 } -> { 816f7000-81710457 } [103512] moving module 04 { 810d1000-81123bbf } -> { 81711000-81763bbf } [338880] moving module 05 { 81124000-81124188 } -> { 81100000-81100188 } [393] moving module 06 { 81125000-813f647f } -> { 81101000-813d247f } [2954368] moving module 07 { 813f7000-816f6fff } -> { 813d3000-816d2fff } [3145728] moving module 03 { 816f7000-81710457 } -> { 816d3000-816ec457 } [103512] moving module 04 { 81711000-81763bbf } -> { 816ed000-8173fbbf } [338880] Scanning fiasco Scanning sigma0 Scanning moe rom/l4Linux.cfg Relocated mbi to [0x8100e000-0x8100e12a] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list 'regions' [ 80001000, 80001b3f] { b40} Kern fiasco [ 80002000, 80072fff] { 71000} Kern fiasco [ 80090000, 800965fb] { 65fc} Sigma0 sigma0 [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 [ 80140000, 8016cacb] { 2cacc} Root moe [ 80170000, 80186f0f] { 16f10} Root moe [ 81000000, 810143f3] { 143f4} Boot bootstrap [ 8100e000, 8100e227] { 228} Root Multiboot info [ 81100000, 8173fbbf] { 63fbc0} Root Module API Version: (87) experimental Sigma0 config ip:80090100 sp:81013de4 Roottask config ip:80140260 sp:00000000 Starting kernel fiasco at 80001300 Hello from Startup::stage2 Cache config: ON ID_PFR[01]: 00001131 00000011 ID_[DA]FR0: 00010400 00000000 ID_MMFR[04]: 01100003 20000000 01202000 00000211 Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rUnversioned director compiled with gcc 4.7.3 for Beagleboard [] Build: #1 Wed Mar 5 17:15:13 CET 2014 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:80000000;80000fff] [0:80073000;8008ffff] [0:80097000;80097fff] [0:8009f000;8013ffff] [4:80140000;8016cfff] [0:8016d000;8016ffff] [4:80170000;80186fff] [0:80187000;8100dfff] [4:8100e000;8100efff] [0:8100f000;810fffff] [4:81100000;8173ffff] [0:81740000;86ffffff] IOMEM:---------------------- [0:0;7fffffff] [0:88000000;ffffffff] MOE: Hello world MOE: found 107500 KByte free memory MOE: found RAM from 80000000 to 87000000 MOE: allocated 112 KByte for the page array @0x80073000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [816d3000-816ec458] [C:503000] l4re BOOTFS: [816ed000-8173fbc0] [C:504000] ned BOOTFS: [81100000-81100189] [C:505000] l4Linux.cfg BOOTFS: [81101000-813d2480] [C:506000] vmlinuz.arm BOOTFS: [813d3000-816d3000] [C:507000] ramdisk-arm.rd MOE: cmdline: moe rom/l4Linux.cfg MOE: Starting: rom/ned rom/l4Linux.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4Linux.cfg' l4Linux | libio: Warning: Query of 'vbus' failed! l4Linux | PH 0 (t: 1) offs=00008000 vaddr=01000000 vend=01331b1c l4Linux | phys=01000000 ephys=01331b1c l4Linux | f_sz=002b33d4 memsz=00331b1c flgs=rwx l4Linux | PH 1 (t: 4) offs=002bb3b0 vaddr=012b33b0 vend=012b33d4 l4Linux | phys=012b33b0 ephys=012b33d4 l4Linux | f_sz=00000024 memsz=00000024 flgs=r-x l4Linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4Linux | phys=00000000 ephys=00000000 l4Linux | f_sz=00000000 memsz=00000000 flgs=rwx l4Linux | Starting binary at 0x10002a0, argc=7 argv=0x80007f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4Linux | External resolver is at 0xa8000794 l4Linux | ======> L4Linux starting... <======== l4Linux | Linux version 3.7.0-l4-svn30 (juliens@ubuntu) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-64) ) #1 Wed May 29 10:25:09 CEST 2013 l4Linux | Binary name: rom/vmlinuz.arm l4Linux | This is an AEABI build. l4Linux | Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh l4Linux | CPU mapping (l:p)[1]: 0:0 l4Linux | Image: 01000000 - 01400000 [4096 KiB]. l4Linux | Areas: Text: 01000000 - 01290000 [2624kB] (a bit longer) l4Linux | Data: 01290000 - 012aeee0 [123kB] l4Linux | Initdata: 01273000 - 0128ed7c [111kB] l4Linux | BSS: 012b33d4 - 01331b1c [505kB] l4Linux | Device scan: l4Linux | Device scan done. l4Linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:01291fa4) l4Linux | main thread will be 413 l4Linux | l4x_register_pointer_section: addr = 01000000 size = 3350528 l4Linux | section-with-init: virt: 0x1000000 to 0x1331b1b [3270 KiB] l4Linux | section-with-init: Phys: 0x80241000 to 0x80572b1c, Size: 3349276 l4Linux | Main thread running, waiting... l4Linux | L4x: Setting superpages for main memory l4Linux | Main memory size: 64MB l4Linux | Main memory: virt: 0x1400000 to 0x53fffff [65536 KiB] l4Linux | Main memory: Phys: 0x81800000 to 0x85800000, Size: 67108864 l4Linux | Filling lower ptabs... l4Linux | Done (220 entries). l4Linux | l4x_register_pointer_section: addr = 01000000 size = 3350528 l4Linux | text: virt: 0x1000000 to 0x1331b1b [3270 KiB] l4Linux | text: Phys: 0x80241000 to 0x80572b1c, Size: 3349276 l4Linux | l4x_rd_path: rom/ramdisk-arm.rd l4Linux | Loading: rom/ramdisk-arm.rd l4Linux | INITRD: Size of RAMdisk is 3072KiB l4Linux | RAMdisk from 0d400000 to 0d700000 [3072KiB] l4Linux | panic: going to sleep forever, bye Kinds regards and thanks for the help, Ismaël Barakat

2 1

Seting Library search path
by Sören Jonsson 06 Mar '14

06 Mar '14

Hello, I am interested in L4 Fiasco as a virtualization environment. I am currently attempting to compile the L4 runtime environment, and I am getting the following error message: === Building package "bootstrap" === ==> Linking bootstrap32.elf /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.7/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: error: ld returned 1 exit status make[5]: *** [bootstrap32.elf] Error 1 make[4]: *** [/home/osj/l4re/build/pkg/bootstrap/server/src/OBJ-amd64_amdfam10] Error 2 make[3]: *** [src] Error 2 make[2]: *** [server] Error 2 make[1]: *** bootstrap] Error 2 make: *** [pkg] Error 2 I have examined the problem, and can see that I have a library /usr/lib/gcc/x86_64-linux-gnu/4.7.2, as well as the /usr/lib/gcc/x86_64-linux-gnu/4.7. Can the problem be that the linker is attempting to link to a dated version of the library, and what is the best way to resolve this problem? Best regards, Sören Jonsson Sweden

2 1

Running application can't create a file
by Irvanda Kurniadi 03 Mar '14

03 Mar '14

Hi, Recently I'm using libtiff library on L4/Fiasco. I can use some function from that library. But when I'm trying to create an image by using libtiff function, I got this error message: TIFFOpen: output.tif: Cannot open. Could not open output.tif for writing MOE: task 1561539 exited with 42 Here is my configuration in module.list entry tiff_test2 roottask moe --init=rom/tiff_test2 module l4re module tiff_test2 I compile and run it over linux and it works properly. This application is supposed to create the output file and then open it by TIFFOpen function. So, I think there is a trick to launch this tiff application over L4/fiasco, so the kernel can permit the application to create a file. But, it's only my assumption and I'm not really sure about this. If by any chance you know something about it, please let me know. Thanks regards, Irvanda

2 3

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 March 2014