diff options
| -rw-r--r-- | lib9p/9P2000.txt | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/lib9p/9P2000.txt b/lib9p/9P2000.txt index 3fb9e51..98ed952 100644 --- a/lib9p/9P2000.txt +++ b/lib9p/9P2000.txt @@ -112,16 +112,17 @@ bitfield o 8 6/RCLOSE # remove-on-close #7/unused - READ = 0 - WRITE = 1 - RDWR = 2 - EXEC = 3 + READ = 0 # unlock read() + WRITE = 1 # unlock write() + RDWR = 2 # unlock read() and write() + EXEC = 3 # unlock read() for files, walk() for directorie # In the 9P protocol, each message has a type, and message types come -# in pairs (except "Rerror"); "T" and "R"; "T" messages are -# client->server requests, and "R" messages are server->client -# responses (I do not know what the Plan 9 designers intended "T" and -# "R" to stand for). The type of a message is represented by a u8 ID. +# in pairs (except "Rerror"); "T" and "R"; T-messages are +# client->server requests, and R-messages are server->client responses +# (the client "Transmits" T-messages and "Receives" R-messages). The +# type of a message is represented by a u8 ID; T-messages are even and +# R-messages are odd. 100/Tversion = "max_msg_size[4] version[s]" 101/Rversion = "max_msg_size[4] version[s]" 102/Tauth = "afid[4] uname[s] aname[s]" @@ -139,7 +140,7 @@ bitfield o 8 114/Tcreate = "fid[4] name[s] perm[dm] mode[o]" 115/Rcreate = "qid[qid] iounit[4]" 116/Tread = "fid[4] offset[8] count[4]" -117/Rread = "data[d]" # for directories data is the sequence "cnt*(entries[stat])" +117/Rread = "data[d]" # for directories, `data` is the sequence "cnt*(entries[stat])" 118/Twrite = "fid[4] offset[8] data[d]" 119/Rwrite = "count[4]" 120/Tclunk = "fid[4]" |