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

- Use the more appropriate devicename element instead of filename

Browse source 
PR:		docs/123422
Submitted by:	pgj
This commit is contained in:
Gabor Kovesdan 2008-05-06 12:49:18 +00:00
parent 9799e078cb
commit 09b1c8d289
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=31958
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -864,7 +864,7 @@ sio3: type 16550A</screen>
<para>The <filename>/etc/ttys</filename> file lists all of the ports
on your FreeBSD system where you want to allow logins. For example,
the first virtual console <filename>ttyv0</filename> has an entry in
the first virtual console <devicename>ttyv0</devicename> has an entry in
this file. You can log in on the console using this entry. This
file also contains entries for the other virtual consoles, serial ports,
and pseudo-ttys. For a hardwired terminal, just list the serial
@ -875,8 +875,8 @@ sio3: type 16550A</screen>
<para>A default FreeBSD install includes an
<filename>/etc/ttys</filename> file with support for the first
four serial ports: <filename>ttyd0</filename> through
<filename>ttyd3</filename>. If you are attaching a terminal
four serial ports: <devicename>ttyd0</devicename> through
<devicename>ttyd3</devicename>. If you are attaching a terminal
to one of those ports, you do not need to add another entry.</para>
<example id="ex-etc-ttys">
@ -1054,7 +1054,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
<para>You should see an entry for the terminal. For
example, the following display shows that a
<command>getty</command> is running on the second serial
port <literal>ttyd1</literal> and is using the
port <devicename>ttyd1</devicename> and is using the
<literal>std.38400</literal> entry in
<filename>/etc/gettytab</filename>:</para>
@ -1443,7 +1443,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
<programlisting>ttyd0 "/usr/libexec/getty <replaceable>xxx</replaceable>" dialup on</programlisting>
<para>The first item in the above line is the device special file for
this entry &mdash; <literal>ttyd0</literal> means
this entry &mdash; <devicename>ttyd0</devicename> means
<filename>/dev/ttyd0</filename> is the file that this
<command>getty</command> will be watching. The second item,
<literal>"/usr/libexec/getty
@ -1726,7 +1726,7 @@ AT&amp;B2&amp;W</programlisting>
<para>If you do not see any <command>getty</command> processes waiting
to open the desired
<filename>ttyd<replaceable>N</replaceable></filename> port,
<devicename>ttyd<replaceable>N</replaceable></devicename> port,
double-check your entries in <filename>/etc/ttys</filename> to see
if there are any mistakes there. Also, check the log file
<filename>/var/log/messages</filename> to see if there are any log
@ -2151,7 +2151,7 @@ raisechar=^^</programlisting>
<para>Edit <filename>/etc/ttys</filename> and change
<literal>off</literal> to <literal>on</literal> and
<literal>dialup</literal> to <literal>vt100</literal> for the
<literal>ttyd0</literal> entry. Otherwise a password will not be
<devicename>ttyd0</devicename> entry. Otherwise a password will not be
required to connect via the serial console, resulting in a
potential security hole.</para>
</step>
@ -2771,7 +2771,7 @@ ttyd1 "/usr/libexec/getty std.9600" unknown off secure
ttyd2 "/usr/libexec/getty std.9600" unknown off secure
ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
<para><literal>ttyd0</literal> through <literal>ttyd3</literal>
<para><devicename>ttyd0</devicename> through <devicename>ttyd3</devicename>
corresponds to <devicename>COM1</devicename> through
<devicename>COM4</devicename>. Change <literal>off</literal> to
<literal>on</literal> for the desired port. If you have changed the