Joe Bryan

Rather than an explicit whitelist, ensuring that clay mountpoint names (ie, desks) conform to `(sane %tas)` is probably the simplest way to accomplish this. That would need to be done...

Apparently `SIGILL` is normal during openssl setup on arm, see https://stackoverflow.com/questions/25708907/ssl-library-init-cause-sigill-when-running-under-gdb. Can you try again, first setting `handle SIGILL nostop noprint` to let the library generate and catch that exception?

@bazfum sorry for the delay. I'm not sure what to make of this trace. It looks like it might be a double free, or trying to free a pointer into...

@darighost such a PR would be welcome, we shouldn't be using the unchecked versions of those string functions.

Worth noting that `|mass` and `|pack` also dirty every page of the snapshot (due to "intrusive" metadata accounting), so running those frequently will result in significant write amplification.

I've updated this driver to target the WIP vane from urbit/urbit#6932 (`%mesa`). Note that most of these changes were first staged on the `yu/mesa` branch of this repo.

It's also possible to configure linux to allow any binary to bind lower ports. It'd be good to mention this option in our docs: ``` sysctl net.ipv4.ip_unprivileged_port_start=80 ``` or ```...

`$pier/.run meld` or `urbit meld $pier`, same for pack.

For posterity, the issue fixed by `--no-demand` or increasing the vm mapping limit is `mprotect: fail: Out of memory`. I still don't know why you were initially seeing `loom: corrupt`...

That's `mprotect()` returning `ENOMEM`, which almost certainly means that we were trying to exceed the kernels max number of virtual-memory mappings (`vm.max_map_count`). `mprotect()` can increase the number of mappings by...