d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Delete MAKEDEV references and update the text about /dev/foo control

Browse Source 
devices that return the next available device when opened.

PR:		50280, 50281, 50282, 50283
Submitted by:	Sergey A.Osokin <osa@FreeBSD.org.ru>
This commit is contained in:
Giorgos Keramidas 2003-03-25 14:49:02 +00:00
parent 12c63b8e4b
commit 5eef84809c
4 changed files with 5 additions and 77 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
share/man/man4/pcm.4
View File

@ -148,33 +148,6 @@ device probed at boot time.
Device probe messages can be examined with the
.Xr dmesg 8
utility.
.Pp
On systems with
.Xr devfs 5 ,
supported device nodes will be created automatically.
For systems without
.Xr devfs 5 ,
appropriate device nodes and symbolic links for the
.Ql pcm0
device can be created with the following commands:
.Bd -literal -offset indent
cd /dev; sh MAKEDEV snd0
.Ed
.Pp
Similarly, the device nodes and symbolic links for the
.Ql pcm1
device would be created as follows:
.Bd -literal -offset indent
cd /dev; sh MAKEDEV snd1
.Ed
.Pp
Since the
.Pa /dev/MAKEDEV
utility creates symbolic links that will be used by
many utilities by default,
the device nodes and symbolic links for the
preferred audio device in systems with multiple audio devices
should be created last.
.Sh DIAGNOSTICS AND TROUBLESHOOTING
.Bl -tag -width 2m
.It ac97: dac not ready

22
share/man/man4/tap.4
View File

@ -45,27 +45,9 @@ module is unloaded (if
.Nm
is built into your kernel, the network interfaces cannot be removed).
.Pp
On older systems without
.Xr devfs 5
support,
.Xr MAKEDEV 8
should be used to create the initial control devices and the task
of locating an unused device is left up to the opener (a
.Nm
device is usually obtained by attempting to open
.Pa /dev/tap0 ,
and if that fails
.Pa /dev/tap1
etc., until an
.Va errno
of
.Er EBUSY
is not received).
.Pp
On systems with
.Xr devfs 5
support,
The
.Nm
interface
permits opens on the special control device
.Pa /dev/tap .
When this device is opened,

26
share/man/man4/tun.4
View File

@ -46,27 +46,9 @@ module is unloaded (if
.Nm
is built into your kernel, the network interfaces cannot be removed).
.Pp
On older systems without
.Xr devfs 5
support,
.Xr MAKEDEV 8
should be used to create the initial control devices and the task
of locating an unused device is left up to the opener (a
.Nm
device is usually obtained by attempting to open
.Pa /dev/tun0 ,
and if that fails
.Pa /dev/tun1
etc., until an
.Va errno
of
.Er EBUSY
is not received).
.Pp
On systems with
.Xr devfs 5
support,
The
.Nm
interface
permits opens on the special control device
.Pa /dev/tun .
When this device is opened,
@ -298,9 +280,7 @@ them pile up.
.Xr inet 4 ,
.Xr intro 4 ,
.Xr pty 4 ,
.Xr devfs 5 ,
.Xr ifconfig 8 ,
.Xr MAKEDEV 8
.Xr ifconfig 8
.Sh AUTHORS
This manual page was originally obtained from
.Nx .

7
share/man/man4/ukbd.4
View File

@ -52,13 +52,6 @@ config file:
.Pp
.Dl "options KBD_INSTALL_CDEV"
.Pp
Go to
.Pa /dev
and make device nodes
.Pa kbd* :
.Pp
.Dl "sh MAKEDEV kbd0 kbd1"
.Pp
If both an AT keyboard USB keyboards are used at the same time, the
AT keyboard will appear as
.Pa kbd0