3 intro \- introduction to the Plan 9 devices
7 implements a file tree for client processes.
8 A file name beginning with a pound sign, such as
10 names the root of a file tree implemented by
12 .IR "kernel device driver"
13 identified by the character after the pound sign.
14 Such names are usually bound to conventional locations
19 bind("#c", "/dev", MREPL)
26 will list the files provided by the
30 A kernel device driver is a
32 in the sense of the Plan 9 File Protocol, 9P (see Section 5),
33 but with the messages implemented by local
34 rather than remote procedure calls.
35 Also, several of the messages
41 have no subroutine equivalents.
43 When a system call is passed a file name beginning with
45 it looks at the next character, and if that is a valid
49 on the corresponding device to get a channel representing the
50 root of that device's file tree.
51 If there are any characters after the device character but
54 or end of string, those characters are passed as parameter
56 to the attach. For example,
62 identifies the number 2 IP protocol stack
66 Each kernel device has a conventional place at which to be bound
70 sections of the following pages includes a
72 command to put the device in the conventional place.
73 Most of these binds are done automatically by
87 commands will need quotes to protect the