On Sun, Nov 7, 2021 at 6:27 PM Samuel Thibault <[email protected]> wrote: > libnetfs does not this way, see libnetfs/dir-lookup.c, it'll first look > for self/, then for the rest, directory by directory.
I know — that's one of my major gripes with libnetfs. Resolving paths component-by-component is _really not_ what you want for a network file system. That's terrible for latency, and moreover, the intermediary paths might not even 'exist' for something like httpfs (https://lists.gnu.org/archive/html/bug-hurd/ is a thing, https://lists.gnu.org/archive/ is not). You can get around that by redefining netfs_S_dir_lookup (); but then you lose most of the point of using netfs. I ended up doing that for my (unpublished) attempt at implementing a 9P translator anyway. Sergey
