mirror of
https://github.com/9fans/plan9port.git
synced 2025-01-12 11:10:07 +00:00
man9: rename IM to MR
Commit d32deab17b
renamed IM to MR but
these man pages were missed.
This commit is contained in:
parent
0144f87dc6
commit
36cd4c58c1
11 changed files with 27 additions and 27 deletions
|
@ -21,7 +21,7 @@ such a machine is called, somewhat confusingly, a
|
|||
Another possibility for a server is to synthesize
|
||||
files on demand, perhaps based on information on data structures
|
||||
maintained in memory; the
|
||||
.IM plumber (4)
|
||||
.MR plumber (4)
|
||||
server is an example of such a server.
|
||||
.PP
|
||||
A
|
||||
|
@ -63,7 +63,7 @@ bytes of data.
|
|||
Text strings are represented this way,
|
||||
with the text itself stored as a UTF-8
|
||||
encoded sequence of Unicode characters (see
|
||||
.IM utf (7) ).
|
||||
.MR utf (7) ).
|
||||
Text strings in 9P messages are not
|
||||
.SM NUL\c
|
||||
-terminated:
|
||||
|
@ -114,7 +114,7 @@ Plan 9 names may contain any printable character (that is, any character
|
|||
outside hexadecimal 00-1F and 80-9F)
|
||||
except slash.)
|
||||
Messages are transported in byte form to allow for machine independence;
|
||||
.IM fcall (3)
|
||||
.MR fcall (3)
|
||||
describes routines that convert to and from this form into a machine-dependent
|
||||
C structure.
|
||||
.SH MESSAGES
|
||||
|
@ -348,7 +348,7 @@ a ``current file'' on the server.
|
|||
Fids are somewhat like file descriptors in a user process,
|
||||
but they are not restricted to files open for I/O:
|
||||
directories being examined, files being accessed by
|
||||
.IM stat (3)
|
||||
.MR stat (3)
|
||||
calls, and so on \(em all files being manipulated by the operating
|
||||
system \(em are identified by fids.
|
||||
Fids are chosen by the client.
|
||||
|
@ -461,7 +461,7 @@ to have their input or output attached to fids on 9P servers.
|
|||
See
|
||||
.IR openfd (9p)
|
||||
and
|
||||
.IM 9pclient (3)
|
||||
.MR 9pclient (3)
|
||||
for details.
|
||||
.PP
|
||||
The
|
||||
|
@ -475,7 +475,7 @@ access permissions (read, write and execute for owner, group and public),
|
|||
access and modification times, and
|
||||
owner and group identifications
|
||||
(see
|
||||
.IM stat (3) ).
|
||||
.MR stat (3) ).
|
||||
The owner and group identifications are textual names.
|
||||
The
|
||||
.B wstat
|
||||
|
@ -523,12 +523,12 @@ into 9P messages.
|
|||
.SS Unix
|
||||
On Unix, 9P services are posted as Unix domain sockets in a
|
||||
well-known directory (see
|
||||
.IM getns (3)
|
||||
.MR getns (3)
|
||||
and
|
||||
.IM 9pserve (4) ).
|
||||
.MR 9pserve (4) ).
|
||||
Clients connect to these servers using a 9P client library
|
||||
(see
|
||||
.IM 9pclient (3) ).
|
||||
.MR 9pclient (3) ).
|
||||
.SH DIRECTORIES
|
||||
Directories are created by
|
||||
.B create
|
||||
|
|
|
@ -122,7 +122,7 @@ and
|
|||
and
|
||||
.I fsauth
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
generate
|
||||
.B attach
|
||||
and
|
||||
|
@ -163,6 +163,6 @@ transactions.
|
|||
.\" .B mount
|
||||
.\" system call on an uninitialized connection.
|
||||
.SH SEE ALSO
|
||||
.IM 9pclient (3) ,
|
||||
.MR 9pclient (3) ,
|
||||
.IR version (9P),
|
||||
Plan 9's \fIauthsrv\fR(6)
|
||||
|
|
|
@ -41,7 +41,7 @@ generated by
|
|||
and
|
||||
.I fsunmount
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
and indirectly by other actions such as failed
|
||||
.I fsopen
|
||||
calls.
|
||||
|
|
|
@ -99,11 +99,11 @@ flushing a
|
|||
and flushing an invalid tag.
|
||||
.SH ENTRY POINTS
|
||||
The
|
||||
.IM 9pclient (3)
|
||||
.MR 9pclient (3)
|
||||
library does not generate
|
||||
.B flush
|
||||
transactions..
|
||||
.IM 9pserve (4)
|
||||
.MR 9pserve (4)
|
||||
generates
|
||||
.B flush
|
||||
transactions to cancel transactions pending when a client hangs up.
|
||||
|
|
|
@ -160,7 +160,7 @@ in this case, the
|
|||
.I fscreate
|
||||
call
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
uses
|
||||
.B open
|
||||
with truncation.
|
||||
|
@ -209,7 +209,7 @@ again.
|
|||
and
|
||||
.I fscreate
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
both generate
|
||||
.B open
|
||||
messages; only
|
||||
|
|
|
@ -43,18 +43,18 @@ it cannot be
|
|||
.PP
|
||||
.I Openfd
|
||||
is implemented by
|
||||
.IM 9pserve (4) .
|
||||
.MR 9pserve (4) .
|
||||
9P servers that post their services using
|
||||
.IM 9pserve (4)
|
||||
.MR 9pserve (4)
|
||||
(or indirectly via
|
||||
.IM post9pservice (3) )
|
||||
.MR post9pservice (3) )
|
||||
will never see a
|
||||
.B Topenfd
|
||||
message.
|
||||
.SH ENTRY POINTS
|
||||
.I Fsopenfd
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
generates an
|
||||
.B openfd
|
||||
message.
|
||||
|
|
|
@ -114,7 +114,7 @@ to be transferred atomically.
|
|||
and
|
||||
.I fswrite
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
generate the corresponding messages.
|
||||
Because they take an offset parameter, the
|
||||
.I fspread
|
||||
|
|
|
@ -45,7 +45,7 @@ so other fids typically remain usable.
|
|||
.SH ENTRY POINTS
|
||||
.I Fsremove
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
generates
|
||||
.B remove
|
||||
messages.
|
||||
|
|
|
@ -88,7 +88,7 @@ The
|
|||
and
|
||||
.I convD2M
|
||||
routines (see
|
||||
.IM fcall (3) )
|
||||
.MR fcall (3) )
|
||||
convert between directory entries and a C structure called a
|
||||
.BR Dir .
|
||||
.PP
|
||||
|
@ -263,7 +263,7 @@ messages are generated by
|
|||
and
|
||||
.IR fsdirstat
|
||||
(see
|
||||
.IM 9pclient (3) ).
|
||||
.MR 9pclient (3) ).
|
||||
.PP
|
||||
.B Wstat
|
||||
messages are generated by
|
||||
|
|
|
@ -91,7 +91,7 @@ requests is called a
|
|||
.SH ENTRY POINTS
|
||||
.I Fsversion
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
generates
|
||||
.B version
|
||||
messages;
|
||||
|
|
|
@ -149,13 +149,13 @@ may be packed in a single message.
|
|||
This constant is called
|
||||
.B MAXWELEM
|
||||
in
|
||||
.IM fcall (3) .
|
||||
.MR fcall (3) .
|
||||
Despite this restriction, the system imposes no limit on the number of elements in a file name,
|
||||
only the number that may be transmitted in a single message.
|
||||
.SH ENTRY POINTS
|
||||
.I Fswalk
|
||||
(see
|
||||
.IM 9pclient (3) )
|
||||
.MR 9pclient (3) )
|
||||
generates walk messages.
|
||||
One or more walk messages may be generated by
|
||||
any call that evaluates file names:
|
||||
|
|
Loading…
Reference in a new issue