|
|
1.1 root 1:
2:
3: mknod Command mknod
4:
5:
6:
7:
8: Make a special file or named pipe
9:
10: /eettcc/mmkknnoodd _f_i_l_e_n_a_m_e _t_y_p_e _m_a_j_o_r _m_i_n_o_r
11: /eettcc/mmkknnoodd _f_i_l_e_n_a_m_e pp
12:
13: In the first form, mknod creates a special file, which provides
14: access to a device by the filename specified. Special files are
15: conventionally stored in the /dev directory.
16:
17: type can be either `b' (for block-special file) or `c' (for
18: character-special file). Block-special files tend to be devices
19: such as disks or magnetic tape, upon which COHERENT uses an
20: elaborate buffering strategy. Character-special files are un-
21: structured (character at a time) devices such as terminals, line
22: printers, or communications devices. Character-special files may
23: also be random-access devices; this circumvents system buffering,
24: allowing transfers of arbitrary size directly between the user
25: and the hardware.
26:
27: The major device number uniquely identifies a device driver to
28: COHERENT. The minor device number is a parameter interpreted by
29: the driver; it might specify the channel of a multiplexor or the
30: unit number of a drive.
31:
32: The caller must be the superuser.
33:
34: In the second form, mknod creates a pipe with the given filename.
35: Named pipes can be used for communication between processes.
36:
37: ***** Files *****
38:
39: /dev/*
40:
41: ***** See Also *****
42:
43: commands, mount
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.