Skip to content

forward p9p services into remote #228

Description

@rjkroege

I noted that my Darwin client's entire disk was available on the Linux remote in /tmp/cpu.

So I (naïve maybe) tried:

# ...cpu to remote...
; NAMESPACE=/tmp/cpu/tmp/ns.rjkroege.:0
; ls $NAMESPACE
acme  acme.log  plumb
; 9p ls acme
9p: mount: dial unix!/tmp/cpu/tmp/ns.rjkroege.:0/acme: connect /tmp/cpu/tmp/ns.rjkroege.:0/acme: Connection refused

So: it would be nice to have the client's P9P namespace brought into the remote (semi)automatically. Or maybe I'm just doing it wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions