Adam Wick

By calling back into GHC for a bunch of critical POSIX functions, we break the "unsafe" assumption in the base library. So HaLVM GHCs will need to revoke those unsafe...

From Alex: Hi Adam, The `alex-3.1.7` package from hvr's PPA doesn't seem to include a `lib/` directory, causing `make install` to fail (see attached). `sudo mkdir /opt/alex/3.1.7/lib` fixes the problem....

Please don't try to do this from first principles. Instead, let's figure out what core `musl` upcalls we can't write in a generic manner, and use those as the requirements....

POSIX is deeply annoying for any number of reasons; one of them is that it mixes up "file descriptors" between files and network sockets, because blah blah blah. What this...

Preferably via Solo5, already included.

Preferably via connections to `mini-os`, already included.

This should be the most obvious, easy port: porting HaLVM3's interface (see #111) to the raw Linux kernel. Given that `musl` has calls for this, I think we should be...

Many of the upcalls that `musl` will make into our fake Linux kernel are going to be generic across all the platforms, or have obvious defaults that work for most...

Write the backend functions for `musl` that deal with networking; I believe they'll all need to start with `syscall_SYS_` or `socketcall`. These should either (1) check for an implementation provided...

Write the backend functions for `musl` that deal with the file system; I believe they'll all need to start with `syscall_SYS_` and the like. These should either (1) check for...