attach

attach and nop - messages to initiate activity

Synopsis

Tnop    tag [2]
Rnop    tag [2]
Tattach tag [2] fid [2] uid [28] aname [28]
Rattach tag [2] fid [2] qid [8]

Description

The nop Transaction

The nop request does nothing overt but may be used to synchronize the channel initially.

The tag should be notag (value 16rFFFF) for a nop message.

The attach Transaction

The attach message serves as a fresh introduction from a user on the client machine to a server. The message identifies the user (uid) and may select the file tree to access (aname).

As a result of the attach transaction, the client will have a connection to the root directory of the desired file tree, represented by fid. An error is returned if fid is already in use. The server's idea of the root of the file tree is represented by the returned qid.

An attach transaction will be generated for kernel devices (see Inferno Devices) when a system call evaluates a file name beginning with #. A mount call (see bind) generates an attach message to the remote file server. When the kernel boots, an attach is made to the root device, root, and then an attach is made to the requested file server machine.

attach

Synopsis

Description

The nop Transaction

The attach Transaction

Entry Points

See Also