Will

Main issue to flag is that we expect most common clients to not have root access / raw socket support, which will limit the ability of the client to control...

It's probably worth differentiating mix-in libraries that can be added to services from the core runtime standard library

I'll split out kernel choice (and architecture) into a separate issue, since that's a separate problem. The other option for xhyve is the https://github.com/moby/hyperkit setup docker uses, which calls xhyve...

as a prefix: this is indeed quite a rabbit hole 🐇 hyperkit / xhyve had two potential PCI drivers that are options for exposing data from the host into the...

> What do you mean by "a public IP that is in a different /16 from " ? for another node with an IP of `a.b.c.d`, you would not ask...

Heuristics to mitigate this include #46 and #47

They'll all be "public" IPs, so we'll need some heuristic for deciding that we've hit some router along the way with an IP that diverges significantly from those of the...

How bad would it be to keep an LRU map of path->verifier? verifier could then just be a randomly chosen number but would be stable until either it falls out...

If this library keeps a cache, it could cache the previous read of the directory contents for the verifier. While that read stays in memory, the verifier remains valid for...

I believe there is a partial migration to the io.FS interface that's living in a branch: https://github.com/willscott/go-nfs/tree/feat/iofs I think the main thing we ran into is that like billy, io.FS...