Enrico Granata

There are two axes at work here - and in fact 3: - can a service "fail" without causing a system-wide panic? - should a service be fire-and-forget or should...

``` In file included from ../../gcc-7.2.0/gcc/c/c-lang.c:22:0: ../../gcc-7.2.0/gcc/system.h:221:11: fatal error: algorithm: No such file or directory # include ^~~~~~~~~~~ compilation terminated. ``` Alas, while we do have the C++ header, it...

This problem is a fair bit more subtle than just make a custom include to point to : ``` /bin/bash ../../gcc-7.2.0/gcc/mkconfig.sh bconfig.h g++ -c -DIN_GCC -DGENERATOR_FILE -I. -Ibuild -I../../gcc-7.2.0/gcc -I../../gcc-7.2.0/gcc/build...

The technical part of this problem can be solved by bootstrapping - but doing that requires an intermediate step where one patches GCC to configure it to work for Puppy.

Signals have pretty bad ergonomics, mostly due to their entirely asynchronous nature, which means that userspace can do very little safely and must essentially set a flag somewhere and return,...

Apropos nothing... http://man7.org/linux/man-pages/man2/vfork.2.html

Instead of doing this, I wrote a couple of nice helper classes for the SMBIOS driver that represent a MemFS file backed by a string and by an integer printed...

This is the content of the kernel log right before the panic: ``` [480] kernel/src/syscalls/impl/logging.cpp:28 (USERSPACE) (pid=9) shell is up and running [480] kernel/src/process/manager.cpp:443 saving FP state for process 9...

``` [0.763] kernel/src/panic/panic.cpp:40 kernel panic at kernel/src/process/manager.cpp:707 - process enqueued for execution multiple times [0.763] kernel/src/process/dumperror.cpp:26 irq: 6 error code: 0 [0.763] kernel/src/process/dumperror.cpp:44 register cr0: 8001003b [0.763] kernel/src/process/dumperror.cpp:45 register cr2:...

This most urgent of tasks is currently blocked on https://github.com/micropython/micropython-lib/issues/318