All the bits about MAKEDEV and mknod should be removed. They haven't
been necessary since 4.x. Noted by: jhb Approved by: bcr (mentor)
This commit is contained in:
parent
8c7cad2cf5
commit
c7122fa8aa
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=40988
2 changed files with 1 additions and 42 deletions
en_US.ISO8859-1/books/arch-handbook
|
@ -43,7 +43,6 @@
|
||||||
linker facility `kld'.</para>
|
linker facility `kld'.</para>
|
||||||
|
|
||||||
<indexterm><primary>device nodes</primary></indexterm>
|
<indexterm><primary>device nodes</primary></indexterm>
|
||||||
<indexterm><primary>MAKEDEV</primary></indexterm>
|
|
||||||
|
|
||||||
<para>Most devices in a &unix;-like operating system are accessed
|
<para>Most devices in a &unix;-like operating system are accessed
|
||||||
through device-nodes, sometimes also called special files.
|
through device-nodes, sometimes also called special files.
|
||||||
|
@ -155,46 +154,6 @@ KMOD=skeleton
|
||||||
</sect2>
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="driverbasics-access">
|
|
||||||
<title>Accessing a Device Driver</title>
|
|
||||||
|
|
||||||
<para>&unix; provides a common set of system calls for user
|
|
||||||
applications to use. The upper layers of the kernel dispatch
|
|
||||||
these calls to the corresponding device driver when a user
|
|
||||||
accesses a device node. The <command>/dev/MAKEDEV</command>
|
|
||||||
script makes most of the device nodes for your system but if you
|
|
||||||
are doing your own driver development it may be necessary to
|
|
||||||
create your own device nodes with
|
|
||||||
<command>mknod</command>.</para>
|
|
||||||
|
|
||||||
<sect2>
|
|
||||||
<title>Creating Static Device Nodes</title>
|
|
||||||
|
|
||||||
<indexterm><primary>device nodes</primary><secondary>static</secondary></indexterm>
|
|
||||||
<indexterm><primary>mknod</primary></indexterm>
|
|
||||||
|
|
||||||
<para>The <command>mknod</command> command requires four
|
|
||||||
arguments to create a device node. You must specify the name
|
|
||||||
of the device node, the type of device, the major number of
|
|
||||||
the device, and the minor number of the device.</para>
|
|
||||||
</sect2>
|
|
||||||
|
|
||||||
<sect2>
|
|
||||||
<title>Dynamic Device Nodes</title>
|
|
||||||
|
|
||||||
<indexterm><primary>device nodes</primary><secondary>dynamic</secondary></indexterm>
|
|
||||||
<indexterm><primary>devfs</primary></indexterm>
|
|
||||||
|
|
||||||
<para>The device filesystem, or devfs, provides access to the
|
|
||||||
kernel's device namespace in the global filesystem namespace.
|
|
||||||
This eliminates the problems of potentially having a device
|
|
||||||
driver without a static device node, or a device node without
|
|
||||||
an installed device driver. Devfs is still a work in
|
|
||||||
progress, but it is already working quite nicely.</para>
|
|
||||||
</sect2>
|
|
||||||
|
|
||||||
</sect1>
|
|
||||||
|
|
||||||
<sect1 id="driverbasics-char">
|
<sect1 id="driverbasics-char">
|
||||||
<title>Character Devices</title>
|
<title>Character Devices</title>
|
||||||
|
|
||||||
|
|
|
@ -5888,7 +5888,7 @@ Label destruction o</programlisting>
|
||||||
or <errorcode>EPERM</errorcode> for lack of privilege.
|
or <errorcode>EPERM</errorcode> for lack of privilege.
|
||||||
This call may be made in a number of situations, including
|
This call may be made in a number of situations, including
|
||||||
as a result of calls to &man.open.2; with
|
as a result of calls to &man.open.2; with
|
||||||
<symbol>O_CREAT</symbol>, &man.mknod.2;, &man.mkfifo.2;, and
|
<symbol>O_CREAT</symbol>, &man.mkfifo.2;, and
|
||||||
others.</para>
|
others.</para>
|
||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue