Expand description
Remote9pMount — a native VFS [Mount] backed by a socket 9P client.
This is the client half of the bidirectional 9P story (#708): where
MountBackend exports a local VFS
[Mount] as a 9P server, Remote9pMount imports a remote 9P2000.L server
and presents it back as a [Mount] the host can
bind_mount into its own namespace. Together
they let hyprstream both serve its namespace to a guest and consume the
guest’s namespace — two independent 9P sessions over two sockets.
It is the native, socket-transport analogue of the wasm-only
WanixMount: the same P9Client-backed
Mount shape, but generic over a genuinely Send + Sync
SocketTransport rather than the browser DMA transport, and with no
unsafe impl Send/Sync (the wasm WanixMount needs one because its DMA
transport is only sound single-threaded). See the crate docs for why the two
are separate types rather than one renamed generic.
§Subject / fid semantics
Every op threads the caller [Subject], exactly like every other VFS
[Mount]. Each walk returns an opaque [Fid] wrapping the remote 9P fid
number; open/read/write/readdir/stat/clunk forward to that fid.
The wrapped P9Client is held behind a single async Mutex so each
Mount op is one atomic T→R exchange on the connection — requests never
interleave on the wire.
Structs§
- Remote9p
Mount - A VFS [
Mount] that forwards every operation to a remote 9P2000.L server over a socketP9Transport.