os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Use <devicename> to mark up device nodes as well.

Browse source 
While I'm here, pour some <replaceable>s on all those cuaaX and ttydX
This commit is contained in:
Udo Erdelhoff 2001-05-22 17:13:11 +00:00
parent ddceddfda4
commit 9a9106675f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9483
2 changed files with 92 additions and 92 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

92
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.199 2001/05/19 15:05:15 dannyboy Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.200 2001/05/20 23:04:46 ue Exp $</pubdate>
<copyright>
<year>1995</year>
@ -2655,7 +2655,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<devicename>vp0</devicename> drivers (the GENERIC kernel
contains everything except <devicename>vp0</devicename>). With
all these drivers present, the Parallel Port drive should be
available as <filename>/dev/da0s4</filename>. Disks can be
available as <devicename>/dev/da0s4</devicename>. Disks can be
mounted using <command>mount /dev/da0s4 /mnt</command> OR (for
dos disks) <command>mount_msdos /dev/da0s4 /mnt</command> as
appropriate.</para>
@ -2763,10 +2763,10 @@ usbd_flags=""</programlisting>
</procedure>
<para>After the system is rebooted, the AT keyboard becomes
<filename>/dev/kbd0</filename> and the USB keyboard becomes
<filename>/dev/kbd1</filename>, if both are connected to the
<devicename>/dev/kbd0</devicename> and the USB keyboard becomes
<devicename>/dev/kbd1</devicename>, if both are connected to the
system. If there is the USB keyboard only, it will be
<filename>/dev/ukbd0</filename>.</para>
<devicename>/dev/ukbd0</devicename>.</para>
<para>If you want to use the USB keyboard in the console, you
have to explicitly tell the console driver to use the existence
@ -2776,7 +2776,7 @@ usbd_flags=""</programlisting>
<screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd1 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
<para>Note that if the USB keyboard is the only keyboard, it is
accessed as <filename>/dev/kbd0</filename>, thus, the command
accessed as <devicename>/dev/kbd0</devicename>, thus, the command
should look like:</para>
<screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd0 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
@ -3690,12 +3690,12 @@ quit</programlisting>
Ridge (long filename) extensions as well.</para>
<para>As an example, if you want to mount the CDROM device,
<filename>/dev/cd0c</filename>, under <filename>/mnt</filename>,
<devicename>/dev/cd0c</devicename>, under <filename>/mnt</filename>,
you would execute:</para>
<screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0c /mnt</userinput></screen>
<para>Note that your device name (<filename>/dev/cd0c</filename>
<para>Note that your device name (<devicename>/dev/cd0c</devicename>
in this example) could be different, depending on the CDROM
interface. Note that the <option>-t cd9660</option> option just
causes the <command>mount_cd9660</command> command to be
@ -5074,7 +5074,7 @@ lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 socksys@ -&gt; /dev/null
crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<para>You just need socksys to go to
<filename>/dev/null</filename> (see &man.null.4;)
<devicename>/dev/null</devicename> (see &man.null.4;)
to fake the open &amp; close. The code in -CURRENT will handle
the rest. This is much cleaner than the way it was done before.
If you want the <devicename>spx</devicename> driver for a local
@ -5776,7 +5776,7 @@ C:\="DOS"</programlisting>
label=FreeBSD</programlisting>
<para>(the above assumes that your FreeBSD slice is known to Linux
as <filename>/dev/hda2</filename>; tailor to suit your setup).
as <devicename>/dev/hda2</devicename>; tailor to suit your setup).
Then, run <command>lilo</command> as <username>root</username> and you should be
done.</para>
@ -6923,8 +6923,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<listitem>
<para>write to kernel memory via
<filename>/dev/mem</filename> and
<filename>/dev/kmem</filename>,</para>
<devicename>/dev/mem</devicename> and
<devicename>/dev/kmem</devicename>,</para>
</listitem>
<listitem>
@ -7040,14 +7040,14 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
</procedure>
<para>All users can now mount the floppy
<filename>/dev/fd0</filename> onto a directory that they
<devicename>/dev/fd0</devicename> onto a directory that they
own:</para>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
<para>Users in group <username>operator</username> can now
mount the cdrom <filename>/dev/cd0c</filename> onto a
mount the cdrom <devicename>/dev/cd0c</devicename> onto a
directory that they own:</para>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
@ -7055,7 +7055,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<para>Unmounting the device is simple:</para>
<screen>&prompt.user; <userinput>umount <filename>~/my-mount-point</filename></userinput></screen>
<screen>&prompt.user; <userinput>umount <filename>~/my-mount-point</></userinput></screen>
<para>Enabling <varname>vfs.usermount</varname>, however, has
negative security implications. A better way to access MSDOS
@ -7128,7 +7128,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
</procedure>
<para>For example, if you are going to move root to
<filename>/dev/ad1s1a</filename>, with
<devicename>/dev/ad1s1a</devicename>, with
<filename>/mnt</filename> as the temporary mount point,
it's:</para>
@ -7353,7 +7353,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
you can configure FreeBSD to support a mouse pointer on each
virtual screen. In order to avoid conflicting with X, syscons
supports a virtual device called
<filename>/dev/sysmouse</filename>. All mouse events received
<devicename>/dev/sysmouse</devicename>. All mouse events received
from the real mouse device are written to the sysmouse device
via moused. If you wish to use your mouse on one or more
virtual consoles, <emphasis>and</emphasis> use X, see
@ -7372,10 +7372,10 @@ Device "/dev/sysmouse"
earlier versions, the <emphasis>Protocol</emphasis> should be
<emphasis>MouseSystems</emphasis>.</para>
<para>Some people prefer to use <filename>/dev/mouse</filename>
under X. To make this work, <filename>/dev/mouse</filename>
<para>Some people prefer to use <devicename>/dev/mouse</devicename>
under X. To make this work, <devicename>/dev/mouse</devicename>
should be linked to
<filename>/dev/sysmouse</filename> (see &man.sysmouse.4;):</para>
<devicename>/dev/sysmouse</devicename> (see &man.sysmouse.4;):</para>
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>rm -f mouse</userinput>
@ -7814,7 +7814,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<programlisting>:0 local /usr/X11R6/bin/X vt4</programlisting>
<para>The above example will direct the X server to run in
<filename>/dev/ttyv3</filename>. Note the number is offset by
<devicename>/dev/ttyv3</devicename>. Note the number is offset by
one. The X server counts the vty from one, whereas the FreeBSD
kernel numbers the vty from zero.</para>
</answer>
@ -7830,7 +7830,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>If you start <application>X</application>
with
<command>startx</command>, the permissions on
<filename>/dev/console</filename> will
<devicename>/dev/console</devicename> will
<emphasis>not</emphasis> get changed, resulting in
things like
<command>xterm -C</command> and
@ -7850,7 +7850,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>is in
<filename>/etc/fbtab</filename> (see &man.fbtab.5;) and it will ensure that whomever logs in on
<filename>/dev/ttyv0</filename> will own the console.</para>
<devicename>/dev/ttyv0</devicename> will own the console.</para>
</answer>
</qandaentry>
@ -8352,7 +8352,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<qandaentry>
<question id="create-dev-net">
<para>I can't create a <filename>/dev/ed0</filename>
<para>I can't create a <devicename>/dev/ed0</devicename>
device!</para>
</question>
@ -10123,12 +10123,12 @@ sio1: type 16550A</programlisting>
<qandaentry>
<question id="missing-tty0X">
<para>I just upgraded to 2.0.5 and my
<devicename>tty0X</devicename> are missing!</para>
<devicename>tty0<replaceable>X</replaceable></devicename> are missing!</para>
</question>
<answer>
<para>Don't worry, they have been merged with the
<devicename>ttydX</devicename> devices. You'll have to change
<devicename>ttyd<replaceable>X</replaceable></devicename> devices. You'll have to change
any old configuration files you have, though.</para>
</answer>
</qandaentry>
@ -10141,21 +10141,21 @@ sio1: type 16550A</programlisting>
<answer>
<para>The third serial port,
<devicename>sio2</devicename>
(see &man.sio.4;, known as COM3 in DOS), is on <filename>/dev/cuaa2</filename>
for dial-out devices, and on <filename>/dev/ttyd2</filename>
(see &man.sio.4;, known as COM3 in DOS), is on <devicename>/dev/cuaa2</devicename>
for dial-out devices, and on <devicename>/dev/ttyd2</devicename>
for dial-in devices. What's the difference between these two
classes of devices?</para>
<para>You use <filename>ttydX</filename> for dial-ins. When
opening <filename>/dev/ttydX</filename> in blocking mode, a
<para>You use <devicename>ttyd<replaceable>X</replaceable></devicename> for dial-ins. When
opening <devicename>/dev/ttyd<replaceable>X</replaceable></devicename> in blocking mode, a
process will wait for the corresponding
<filename>cuaaX</filename> device to become inactive, and then
<devicename>cuaa<replaceable>X</replaceable></devicename> device to become inactive, and then
wait for the carrier detect line to go active. When you open
the <filename>cuaaX</filename> device, it makes sure the serial
port isn't already in use by the <filename>ttydX</filename>
the <devicename>cuaa<replaceable>X</replaceable></devicename> device, it makes sure the serial
port isn't already in use by the <devicename>ttyd<replaceable>X</replaceable></devicename>
device. If the port's available, it <quote>steals</quote> it
from the <filename>ttydX</filename> device. Also, the
<filename>cuaXX</filename> device doesn't care about carrier
from the <devicename>ttyd<replaceable>X</replaceable></devicename> device. Also, the
<devicename>cuaa<replaceable>X</replaceable></devicename> device doesn't care about carrier
detect. With this scheme and an auto-answer modem, you can have
remote users log in and you can still dialout with the same
modem and the system will take care of all the
@ -10216,8 +10216,8 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
</question>
<answer>
<para>The <filename>ttydX</filename> (or
<filename>cuaaX</filename>) device is the regular device
<para>The <devicename>ttyd<replaceable>X</replaceable></devicename> (or
<devicename>cuaa<replaceable>X</replaceable></devicename>) device is the regular device
you'll want to open for your applications. When a process
opens the device, it'll have a default set of terminal I/O
settings. You can see these settings with the command</para>
@ -10244,11 +10244,11 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<para>You can also prevent certain settings from being changed
by an application by making adjustments to the
<quote>lock state</quote> device. For example, to lock the
speed of <filename>ttyd5</filename> to 57600 bps, do</para>
speed of <devicename>ttyd5</devicename> to 57600 bps, do</para>
<screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
<para>Now, an application that opens <filename>ttyd5</filename>
<para>Now, an application that opens <devicename>ttyd5</devicename>
and tries to change the speed of the port will be stuck with
57600 bps.</para>
@ -10296,7 +10296,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<programlisting>ttyd1 "/usr/libexec/getty std.57600" dialup on insecure</programlisting>
<para>This line indicates that the second serial port
(<filename>/dev/ttyd1</filename>) has a modem connected
(<devicename>/dev/ttyd1</devicename>) has a modem connected
running at 57600 bps and no parity
(<literal>std.57600</literal>, which comes from the file
<filename>/etc/gettytab</filename>, see &man.gettytab.5;).
@ -10304,7 +10304,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
The port is <literal>on</literal> and is
<literal>insecure</literal>---meaning root logins on the port
aren't allowed. For dialin ports like this one, use the
<literal>ttydX</literal> entry.</para>
<devicename>ttyd<replaceable>X</replaceable></devicename> entry.</para>
<para>It's common practice to use <literal>dialup</literal> as
the terminal type. Many users set up in their <filename>.profile</filename> or
@ -10355,7 +10355,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<programlisting>ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure</programlisting>
<para>This example shows that the port on
<filename>/dev/ttyd4</filename> has a wyse50 terminal
<devicename>/dev/ttyd4</devicename> has a wyse50 terminal
connected at 38400 bps with no parity
(<literal>std.38400</literal> from
<filename>/etc/gettytab</filename>, see &man.gettytab.5;) and <username>root</username> logins are
@ -10433,17 +10433,17 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<answer>
<para>Make what's called a <quote>direct</quote> entry in your
<filename>/etc/remote</filename> file (see &man.remote.5;). For example, if your modem's hooked
up to the first serial port, <filename>/dev/cuaa0</filename>,
up to the first serial port, <devicename>/dev/cuaa0</devicename>,
then put in the following line:</para>
<programlisting>cuaa0:dv=/dev/cuaa0:br#19200:pa=none</programlisting>
<para>Use the highest bps rate your modem supports in the br
capability. Then, type
<command>tip cuaa0</command> (see &man.tip.1;)
<command>tip <devicename>cuaa0</devicename></command> (see &man.tip.1;)
and you'll be connected to your modem.</para>
<para>If there is no <filename>/dev/cuaa0</filename> on your
<para>If there is no <devicename>/dev/cuaa0</devicename> on your
system, do this:</para>
<screen>&prompt.root; <userinput>cd /dev</userinput>
@ -10454,7 +10454,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
<para>with <replaceable>line</replaceable> being the serial port (e.g.
<filename>/dev/cuaa0</filename>) and <replaceable>speed</replaceable> being the speed
<devicename>/dev/cuaa0</devicename>) and <replaceable>speed</replaceable> being the speed
(e.g.<literal>57600</literal>). When you are done entering
the AT commands hit <literal>~.</literal> to exit.</para>
</answer>

92
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.199 2001/05/19 15:05:15 dannyboy Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.200 2001/05/20 23:04:46 ue Exp $</pubdate>
<copyright>
<year>1995</year>
@ -2655,7 +2655,7 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
<devicename>vp0</devicename> drivers (the GENERIC kernel
contains everything except <devicename>vp0</devicename>). With
all these drivers present, the Parallel Port drive should be
available as <filename>/dev/da0s4</filename>. Disks can be
available as <devicename>/dev/da0s4</devicename>. Disks can be
mounted using <command>mount /dev/da0s4 /mnt</command> OR (for
dos disks) <command>mount_msdos /dev/da0s4 /mnt</command> as
appropriate.</para>
@ -2763,10 +2763,10 @@ usbd_flags=""</programlisting>
</procedure>
<para>After the system is rebooted, the AT keyboard becomes
<filename>/dev/kbd0</filename> and the USB keyboard becomes
<filename>/dev/kbd1</filename>, if both are connected to the
<devicename>/dev/kbd0</devicename> and the USB keyboard becomes
<devicename>/dev/kbd1</devicename>, if both are connected to the
system. If there is the USB keyboard only, it will be
<filename>/dev/ukbd0</filename>.</para>
<devicename>/dev/ukbd0</devicename>.</para>
<para>If you want to use the USB keyboard in the console, you
have to explicitly tell the console driver to use the existence
@ -2776,7 +2776,7 @@ usbd_flags=""</programlisting>
<screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd1 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
<para>Note that if the USB keyboard is the only keyboard, it is
accessed as <filename>/dev/kbd0</filename>, thus, the command
accessed as <devicename>/dev/kbd0</devicename>, thus, the command
should look like:</para>
<screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd0 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
@ -3690,12 +3690,12 @@ quit</programlisting>
Ridge (long filename) extensions as well.</para>
<para>As an example, if you want to mount the CDROM device,
<filename>/dev/cd0c</filename>, under <filename>/mnt</filename>,
<devicename>/dev/cd0c</devicename>, under <filename>/mnt</filename>,
you would execute:</para>
<screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0c /mnt</userinput></screen>
<para>Note that your device name (<filename>/dev/cd0c</filename>
<para>Note that your device name (<devicename>/dev/cd0c</devicename>
in this example) could be different, depending on the CDROM
interface. Note that the <option>-t cd9660</option> option just
causes the <command>mount_cd9660</command> command to be
@ -5074,7 +5074,7 @@ lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 socksys@ -&gt; /dev/null
crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
<para>You just need socksys to go to
<filename>/dev/null</filename> (see &man.null.4;)
<devicename>/dev/null</devicename> (see &man.null.4;)
to fake the open &amp; close. The code in -CURRENT will handle
the rest. This is much cleaner than the way it was done before.
If you want the <devicename>spx</devicename> driver for a local
@ -5776,7 +5776,7 @@ C:\="DOS"</programlisting>
label=FreeBSD</programlisting>
<para>(the above assumes that your FreeBSD slice is known to Linux
as <filename>/dev/hda2</filename>; tailor to suit your setup).
as <devicename>/dev/hda2</devicename>; tailor to suit your setup).
Then, run <command>lilo</command> as <username>root</username> and you should be
done.</para>
@ -6923,8 +6923,8 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<listitem>
<para>write to kernel memory via
<filename>/dev/mem</filename> and
<filename>/dev/kmem</filename>,</para>
<devicename>/dev/mem</devicename> and
<devicename>/dev/kmem</devicename>,</para>
</listitem>
<listitem>
@ -7040,14 +7040,14 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
</procedure>
<para>All users can now mount the floppy
<filename>/dev/fd0</filename> onto a directory that they
<devicename>/dev/fd0</devicename> onto a directory that they
own:</para>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
<para>Users in group <username>operator</username> can now
mount the cdrom <filename>/dev/cd0c</filename> onto a
mount the cdrom <devicename>/dev/cd0c</devicename> onto a
directory that they own:</para>
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
@ -7055,7 +7055,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<para>Unmounting the device is simple:</para>
<screen>&prompt.user; <userinput>umount <filename>~/my-mount-point</filename></userinput></screen>
<screen>&prompt.user; <userinput>umount <filename>~/my-mount-point</></userinput></screen>
<para>Enabling <varname>vfs.usermount</varname>, however, has
negative security implications. A better way to access MSDOS
@ -7128,7 +7128,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
</procedure>
<para>For example, if you are going to move root to
<filename>/dev/ad1s1a</filename>, with
<devicename>/dev/ad1s1a</devicename>, with
<filename>/mnt</filename> as the temporary mount point,
it's:</para>
@ -7353,7 +7353,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
you can configure FreeBSD to support a mouse pointer on each
virtual screen. In order to avoid conflicting with X, syscons
supports a virtual device called
<filename>/dev/sysmouse</filename>. All mouse events received
<devicename>/dev/sysmouse</devicename>. All mouse events received
from the real mouse device are written to the sysmouse device
via moused. If you wish to use your mouse on one or more
virtual consoles, <emphasis>and</emphasis> use X, see
@ -7372,10 +7372,10 @@ Device "/dev/sysmouse"
earlier versions, the <emphasis>Protocol</emphasis> should be
<emphasis>MouseSystems</emphasis>.</para>
<para>Some people prefer to use <filename>/dev/mouse</filename>
under X. To make this work, <filename>/dev/mouse</filename>
<para>Some people prefer to use <devicename>/dev/mouse</devicename>
under X. To make this work, <devicename>/dev/mouse</devicename>
should be linked to
<filename>/dev/sysmouse</filename> (see &man.sysmouse.4;):</para>
<devicename>/dev/sysmouse</devicename> (see &man.sysmouse.4;):</para>
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>rm -f mouse</userinput>
@ -7814,7 +7814,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<programlisting>:0 local /usr/X11R6/bin/X vt4</programlisting>
<para>The above example will direct the X server to run in
<filename>/dev/ttyv3</filename>. Note the number is offset by
<devicename>/dev/ttyv3</devicename>. Note the number is offset by
one. The X server counts the vty from one, whereas the FreeBSD
kernel numbers the vty from zero.</para>
</answer>
@ -7830,7 +7830,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>If you start <application>X</application>
with
<command>startx</command>, the permissions on
<filename>/dev/console</filename> will
<devicename>/dev/console</devicename> will
<emphasis>not</emphasis> get changed, resulting in
things like
<command>xterm -C</command> and
@ -7850,7 +7850,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>is in
<filename>/etc/fbtab</filename> (see &man.fbtab.5;) and it will ensure that whomever logs in on
<filename>/dev/ttyv0</filename> will own the console.</para>
<devicename>/dev/ttyv0</devicename> will own the console.</para>
</answer>
</qandaentry>
@ -8352,7 +8352,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<qandaentry>
<question id="create-dev-net">
<para>I can't create a <filename>/dev/ed0</filename>
<para>I can't create a <devicename>/dev/ed0</devicename>
device!</para>
</question>
@ -10123,12 +10123,12 @@ sio1: type 16550A</programlisting>
<qandaentry>
<question id="missing-tty0X">
<para>I just upgraded to 2.0.5 and my
<devicename>tty0X</devicename> are missing!</para>
<devicename>tty0<replaceable>X</replaceable></devicename> are missing!</para>
</question>
<answer>
<para>Don't worry, they have been merged with the
<devicename>ttydX</devicename> devices. You'll have to change
<devicename>ttyd<replaceable>X</replaceable></devicename> devices. You'll have to change
any old configuration files you have, though.</para>
</answer>
</qandaentry>
@ -10141,21 +10141,21 @@ sio1: type 16550A</programlisting>
<answer>
<para>The third serial port,
<devicename>sio2</devicename>
(see &man.sio.4;, known as COM3 in DOS), is on <filename>/dev/cuaa2</filename>
for dial-out devices, and on <filename>/dev/ttyd2</filename>
(see &man.sio.4;, known as COM3 in DOS), is on <devicename>/dev/cuaa2</devicename>
for dial-out devices, and on <devicename>/dev/ttyd2</devicename>
for dial-in devices. What's the difference between these two
classes of devices?</para>
<para>You use <filename>ttydX</filename> for dial-ins. When
opening <filename>/dev/ttydX</filename> in blocking mode, a
<para>You use <devicename>ttyd<replaceable>X</replaceable></devicename> for dial-ins. When
opening <devicename>/dev/ttyd<replaceable>X</replaceable></devicename> in blocking mode, a
process will wait for the corresponding
<filename>cuaaX</filename> device to become inactive, and then
<devicename>cuaa<replaceable>X</replaceable></devicename> device to become inactive, and then
wait for the carrier detect line to go active. When you open
the <filename>cuaaX</filename> device, it makes sure the serial
port isn't already in use by the <filename>ttydX</filename>
the <devicename>cuaa<replaceable>X</replaceable></devicename> device, it makes sure the serial
port isn't already in use by the <devicename>ttyd<replaceable>X</replaceable></devicename>
device. If the port's available, it <quote>steals</quote> it
from the <filename>ttydX</filename> device. Also, the
<filename>cuaXX</filename> device doesn't care about carrier
from the <devicename>ttyd<replaceable>X</replaceable></devicename> device. Also, the
<devicename>cuaa<replaceable>X</replaceable></devicename> device doesn't care about carrier
detect. With this scheme and an auto-answer modem, you can have
remote users log in and you can still dialout with the same
modem and the system will take care of all the
@ -10216,8 +10216,8 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
</question>
<answer>
<para>The <filename>ttydX</filename> (or
<filename>cuaaX</filename>) device is the regular device
<para>The <devicename>ttyd<replaceable>X</replaceable></devicename> (or
<devicename>cuaa<replaceable>X</replaceable></devicename>) device is the regular device
you'll want to open for your applications. When a process
opens the device, it'll have a default set of terminal I/O
settings. You can see these settings with the command</para>
@ -10244,11 +10244,11 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<para>You can also prevent certain settings from being changed
by an application by making adjustments to the
<quote>lock state</quote> device. For example, to lock the
speed of <filename>ttyd5</filename> to 57600 bps, do</para>
speed of <devicename>ttyd5</devicename> to 57600 bps, do</para>
<screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
<para>Now, an application that opens <filename>ttyd5</filename>
<para>Now, an application that opens <devicename>ttyd5</devicename>
and tries to change the speed of the port will be stuck with
57600 bps.</para>
@ -10296,7 +10296,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<programlisting>ttyd1 "/usr/libexec/getty std.57600" dialup on insecure</programlisting>
<para>This line indicates that the second serial port
(<filename>/dev/ttyd1</filename>) has a modem connected
(<devicename>/dev/ttyd1</devicename>) has a modem connected
running at 57600 bps and no parity
(<literal>std.57600</literal>, which comes from the file
<filename>/etc/gettytab</filename>, see &man.gettytab.5;).
@ -10304,7 +10304,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
The port is <literal>on</literal> and is
<literal>insecure</literal>---meaning root logins on the port
aren't allowed. For dialin ports like this one, use the
<literal>ttydX</literal> entry.</para>
<devicename>ttyd<replaceable>X</replaceable></devicename> entry.</para>
<para>It's common practice to use <literal>dialup</literal> as
the terminal type. Many users set up in their <filename>.profile</filename> or
@ -10355,7 +10355,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<programlisting>ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure</programlisting>
<para>This example shows that the port on
<filename>/dev/ttyd4</filename> has a wyse50 terminal
<devicename>/dev/ttyd4</devicename> has a wyse50 terminal
connected at 38400 bps with no parity
(<literal>std.38400</literal> from
<filename>/etc/gettytab</filename>, see &man.gettytab.5;) and <username>root</username> logins are
@ -10433,17 +10433,17 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<answer>
<para>Make what's called a <quote>direct</quote> entry in your
<filename>/etc/remote</filename> file (see &man.remote.5;). For example, if your modem's hooked
up to the first serial port, <filename>/dev/cuaa0</filename>,
up to the first serial port, <devicename>/dev/cuaa0</devicename>,
then put in the following line:</para>
<programlisting>cuaa0:dv=/dev/cuaa0:br#19200:pa=none</programlisting>
<para>Use the highest bps rate your modem supports in the br
capability. Then, type
<command>tip cuaa0</command> (see &man.tip.1;)
<command>tip <devicename>cuaa0</devicename></command> (see &man.tip.1;)
and you'll be connected to your modem.</para>
<para>If there is no <filename>/dev/cuaa0</filename> on your
<para>If there is no <devicename>/dev/cuaa0</devicename> on your
system, do this:</para>
<screen>&prompt.root; <userinput>cd /dev</userinput>
@ -10454,7 +10454,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
<para>with <replaceable>line</replaceable> being the serial port (e.g.
<filename>/dev/cuaa0</filename>) and <replaceable>speed</replaceable> being the speed
<devicename>/dev/cuaa0</devicename>) and <replaceable>speed</replaceable> being the speed
(e.g.<literal>57600</literal>). When you are done entering
the AT commands hit <literal>~.</literal> to exit.</para>
</answer>