NAME
     aexport - export this deck's files over the mesh

SYNOPSIS
     aexport [on | off]

DESCRIPTION
     Aexport turns on the 9P server that offers this deck's own files to other
     decks over the ther mesh.  It is the far side of dial(1): one deck runs
     aexport on, another dials it and mounts what it finds.

     With no argument, aexport prints whether the export is on.

     What is exported is the deck's local server tree -- /dev, /env, /proc,
     /srv, /n/local and the rest of what this deck itself serves.  A dialer
     attaching with the service name 9fs lands at that root and walks down
     from there, so a file on this deck at /n/local/text/conscience.txt is, on
     the other deck, /n/kes/n/local/text/conscience.txt, for a mount at
     /n/kes.

     Exporting also changes what this deck says about itself: the discovery
     beacon advertises 9fs while the export is on and stops advertising it
     when it goes off, so who(1) on a neighbouring deck shows the service
     appear and disappear.  Nothing advertises a service it is not actually
     serving.

     The export is off at boot and does not survive a reboot.  It is opt-in
     because the server's receive thread holds a four-kilobyte stack out of
     the small pool the deck also spends on shells and outbound connections; a
     deck that is not being read from should not be paying for it.

EXAMPLES
     On the deck with the files -- call it kestrel:

          aexport on
          aexport

     On the other deck:

          who
          srv aether!kestrel!9fs kes
          mount /srv/kes /n/kes
          ls /n/kes/n/local

     When done, from either end:

          unmount /n/kes
          hangup kes
          aexport off

FILES
     /net/aether
          The mesh interface the export is carried over; it must be up.

     /net/aether/self/services
          What this deck advertises.  9fs appears here while the export is on.

SEE ALSO
     dial(1), bind(1), who(1), achat(1), aether(3)

NOTES
     Aexport exists only in builds with both the mesh and the 9P server.
     Without the mesh up it reports that the server is not initialized.

     Anything the deck serves is readable by anything that can reach the
     radio.  The mesh is a shared medium and this is a general-purpose export;
     turn it off when you are not using it.

     LoRa is slow.  Mounting over the mesh is for reading a file and passing a
     message, not for working out of a remote directory.

FRST Computer                                                       AEXPORT(1)
