Dan Gohman

FreeBSD's `flock` does appear to be per-file-description, rather than per-process. I'm going to propose an API which is essentially `flock`, with shared (read-only) and exclusive (read-write) locking. It applies only...

WebAssembly/wasi-filesystem#69 is now merged, and on track to be in preview2. This doesn't yet cover byte ranges or mandatory locking, but those can be considered separately.

Unfortunately, file locking was removed around the time of preview2's release in order to keep the scope down, as there were a lot of other things to do to get...

As the person who initially brought preopens to WASI, based on similar ideas in CloudABI and Capsicum, I agree. I've also come to believe that migrating wasi-filesystem to have a...

A subtlety here is that the current `*-at` functions perform this sandboxing where they prevent ".." and symlinks from escaping the given directory. In contrast, POSIX `openat` doesn't do this...

In a POSIX sense, prepending the path isn't sufficient, because [according to POSIX](https://pubs.opengroup.org/onlinepubs/9699919799/functions/open.html), the main purpose of `openat` is to avoid race conditions: > The purpose of the openat() function...

> Do we actually need to support `openat` without `RESOLVE_BENEATH`? That's a good question. I've been thinking part of the goal here is to have as "normal" a filesystem API...

WASI filesystem allows applications to voluntarily sandbox themselves by closing fds to directories they don't need, or even opening subdirectories and closing the parent fds. My sense here is that...

I've now added a brief mention of how components are organized into sections.

I myself have no interest in m68k. But I will merge PRs if they don't negatively impact other users.