NSPACE(3): name space conventions
; NS=' / / /zx tcp!server!zx ' ; Importzx
DESCRIPTIONThis page describes the conventions for the name space. The importzx(1) command imports the main tree which follows such conventions.
Clive terminals operate on hosted environments. Clive servers may be native (not yet, really) or hosted.
The main tree is usually mounted at
its dump can be found at
/once tree keeps stuff not be dumped. The
dump contains a frozen version of the main tree for each day.
containing a file named
NODUMP are never
copied to the dump. Files with names starting with a dot character
.) are never dumped.
The name space is usually specified by either a environment variable
$NS) or by a file at
$HOME/NS. In both cases, the text describes
the name space. The environment variable may be just the path for a
file describing the name space, and acts as an indirection to that
file in such a case.
The description of the name space is a series of lines, one per mount entry. A line can be a printed directory entry (with attribute/value pairs, as expected). In that case, the path for the directory is used as the mount point and the directory is mounted there.
A line can be also a pair of strings, the first is the path for the mount point and the second refers to the resource mounted there. The resource may be a path, in which case it refers to a local file, or it may be a resource address as described in addr(3), to refer to the addressed resource.
/ / /zx unix!localhost!zx
The name space is a prefix table and the longest prefix wins, but each prefix may have more than one entry (i.e., be a union).
These files can be expected in the name space.
- local terminal binaries for the hosting system
- The Rc shell, always kept at the terminal
- Root of mounted non-archived main tree
- Root of the mounted dumps
Root of dump for
- Copy of files for the named year and day
- Root of the main tree
- Portable scripts. Non portable scripts are kept on a per-architecture directory along with binaries.
- Binaries for OSX on amd64 hosts.
- Binaries for BSD on amd64 hosts.
- Binaries for Linux on amd64 hosts.
- Copy of configuration for servers and terminals
- System wide libraries (eg, bibliography, icons, etc.)
- Copy of system wide e-mail files
- Source for the system
/sysgo compliant, should not be used. Use
- White papers for the system
- Source for manual pages.
- Source for the lsub branch of the go compiler
- System source
- Source for clive packages and binary commands
- Source for clive binary commands
- Source for external go packages (google code, etc.).
- Home and project directories
- Web pages
- Plan9ports copy
- Directory for xcmd(1) to execute commands on lsub systems.
- Commands run at nautilus, see xcmd(1).
run at nautilus, see