3 read, write \- transfer data from and to a file
38 from the file identified by
40 which must be opened for reading,
43 bytes after the beginning of the file.
44 The bytes are returned with the
50 field in the reply indicates the number of bytes returned.
51 This may be less than the requested amount.
54 field is greater than or equal to the number of bytes in the file,
55 a count of zero will be returned.
59 returns an integral number of
60 directory entries exactly as in
64 one for each member of the directory.
67 request message must have
69 equal to zero or the value of
73 on the directory, plus the number of bytes
74 returned in the previous
76 In other words, seeking other than to the beginning
77 is illegal in a directory (see
84 bytes of data be recorded in the file identified by
86 which must be opened for writing, starting
88 bytes after the beginning of the file.
89 If the file is append-only,
90 the data will be placed at the end of the file regardless of
92 Directories may not be written.
96 reply records the number of bytes actually written.
97 It is usually an error
98 if this is not the same as requested.
100 Because 9P implementations may limit the size of individual
102 more than one message may be produced by a single
111 if non-zero, reports the maximum size that is guaranteed
112 to be transferred atomically.
117 messages are generated by the corresponding calls.
118 Because they include an offset, the
122 calls correspond more directly to the 9P messages.
125 affects the offset, it does not generate a message.