Annotated edit history of
null(4) version 1 showing authors affecting page license.
View with all changes included.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
NULL |
|
|
2 |
!!!NULL |
|
|
3 |
NAME |
|
|
4 |
DESCRIPTION |
|
|
5 |
NOTES |
|
|
6 |
FILES |
|
|
7 |
SEE ALSO |
|
|
8 |
---- |
|
|
9 |
!!NAME |
|
|
10 |
|
|
|
11 |
|
|
|
12 |
null, zero - data sink |
|
|
13 |
!!DESCRIPTION |
|
|
14 |
|
|
|
15 |
|
|
|
16 |
Data written on a __null__ or __zero__ special file is |
|
|
17 |
discarded. |
|
|
18 |
|
|
|
19 |
|
|
|
20 |
Reads from the __null__ special file always return end of |
|
|
21 |
file, whereas reads from __zero__ always return 0 |
|
|
22 |
characters. |
|
|
23 |
|
|
|
24 |
|
|
|
25 |
__null__ and __zero__ are typically created |
|
|
26 |
by: |
|
|
27 |
|
|
|
28 |
|
|
|
29 |
mknod -m 666 /dev/null c 1 3 |
|
|
30 |
mknod -m 666 /dev/zero c 1 5 |
|
|
31 |
chown root:root /dev/null /dev/zero |
|
|
32 |
!!NOTES |
|
|
33 |
|
|
|
34 |
|
|
|
35 |
If these devices are not writable and readable for all |
|
|
36 |
users, many programs will act strange. |
|
|
37 |
!!FILES |
|
|
38 |
|
|
|
39 |
|
|
|
40 |
''/dev/null |
|
|
41 |
/dev/zero'' |
|
|
42 |
!!SEE ALSO |
|
|
43 |
|
|
|
44 |
|
|
|
45 |
chown(1), mknod(1) |
|
|
46 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.