NAME
     ns - print the namespace

SYNOPSIS
     ns

DESCRIPTION
     Ns prints the deck's mount table: one line per entry, saying which server
     answers for which part of the file tree.

     This table is the machine.  Every file on the deck -- the console, the
     keyboard, the radio, the flash, a board on the far end of a link -- is
     served by some program, and the table says which program serves what.
     Programs know only paths, so changing an entry changes what a program
     talks to without changing the program.  That is why cat works on the mesh
     and why a remote machine's network can be made to look like this one's.

     Each line is

          server on mountpoint (mode)

     where server is a local server name (cons, env, proc, srv, local, net,
     factotum, ...), a path that was bound there, or a remote connection;
     mountpoint is where it appears; and mode is replace, before or after.  It
     is replace for everything the deck can presently do -- see bind(1).

     A fresh deck shows only the servers set up at boot.  Entries appear as
     you mount and bind, and after tunein(1) the table is the clearest single
     answer to what happened.

EXAMPLES
     Look before touching anything:

          ns

     A deck attuned to a crystal shows roughly this, the last three lines
     being the graft:

          cons on /dev (replace)
          env on /env (replace)
          proc on /proc (replace)
          srv on /srv (replace)
          local on /n/local (replace)
          net on /net (replace)
          bbs.frstcomputer.net on /n/dc (replace)
          /n/dc/net/tcp on /net/tcp (replace)
          /n/dc/rooms on /n/bbs (replace)

     When a command reports a file it cannot find, the question is nearly
     always which server it reached instead:

          ns
          ls /srv

FILES
     /srv Posted connections; a mount reaches one of these.

SEE ALSO
     bind(1), dial(1), tunein(1)

NOTES
     The namespace is per-deck, not per-shell.  A bind made in one shell is
     seen by every other, unlike Plan 9, where each process has its own.

FRST Computer                                                            NS(1)
