diff options
| author | Luke T. Shumaker <lukeshu@lukeshu.com> | 2025-03-28 10:03:44 -0600 |
|---|---|---|
| committer | Luke T. Shumaker <lukeshu@lukeshu.com> | 2025-03-28 11:40:22 -0600 |
| commit | a492c4a31f1c8b2a0d58e24ab957ef3c8f9edfd2 (patch) | |
| tree | 3af2acfb87cec927da720d1541bac89730cd45b5 /lib9p/idl/2002-9P2000.9p | |
| parent | d67db573786da4780653e72879033b9e24e83e28 (diff) | |
lib9p: idl: Touch up the *.9p files
Diffstat (limited to 'lib9p/idl/2002-9P2000.9p')
| -rw-r--r-- | lib9p/idl/2002-9P2000.9p | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib9p/idl/2002-9P2000.9p b/lib9p/idl/2002-9P2000.9p index 2a4f7ed..c569c74 100644 --- a/lib9p/idl/2002-9P2000.9p +++ b/lib9p/idl/2002-9P2000.9p @@ -36,13 +36,13 @@ bitfield dm = 4 "31=DIR" "30=APPEND" "29=EXCL" - # DMMOUNT has been around in Plan 9 forever (CHMOUNT in <4e), + # DMMOUNT has been around in Plan 9 since 2e (CHMOUNT in <4e), # but is undocumented, and is explicitly excluded from the # 9P2000 draft RFC. As I understand it, DMMOUNT indicates # that the file is mounted by the kernel as a 9P transport; # that the kernel has a lock on doing I/O on it, so userspace # can't do I/O on it. - "28=reserved(PLAN9_MOUNT)" + "28=_PLAN9_MOUNT" "27=AUTH" "26=TMP" #... @@ -63,7 +63,7 @@ bitfield qt = 1 "7=DIR" "6=APPEND" "5=EXCL" - "4=reserved(PLAN9_MOUNT)" # See "PLAN9_MOUNT" in "dm" above. + "4=_PLAN9_MOUNT" # See "_PLAN9_MOUNT" in "dm" above. "3=AUTH" # Fun historical fact: QTTMP was a relatively late addition to # Plan 9, in 2003-12. |