3 attach, auth \- messages to establish a connection
34 message serves as a fresh introduction from a user on
35 the client machine to the server.
36 The message identifies the user
39 the file tree to access
43 argument specifies a fid previously established by an
45 message, as described below.
49 transaction, the client will have a connection to the root
50 directory of the desired file tree,
53 An error is returned if
56 The server's idea of the root of the file tree is represented by the returned
59 If the client does not wish to authenticate the connection, or knows that
60 authentication is not required, the
64 message should be set to
70 If the client does wish to authenticate, it must acquire and validate an
74 message before doing the
81 a new fid to be established for authentication, and the
85 that will be those of the following
88 If the server does not require authentication, it returns
94 If the server does require authentication, it returns
96 defining a file of type
100 that may be read and written (using
104 messages in the usual way) to execute an authentication protocol.
105 That protocol's definition is not part of 9P itself.
107 Once the protocol is complete, the same
111 message for the user, granting entry.
114 may be used for multiple
116 messages with the same
123 transaction will be generated for kernel devices
126 when a system call evaluates a file name
130 generates an attach on the kernel device
139 message to the remote file server.
140 When the kernel boots, an
142 is made to the root device,
146 is made to the requested file server machine.
150 transaction is generated by the
152 system call or by the first
154 system call on an uninitialized connection.