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

Various grammar fixes.

Browse source 
Translators can safely ignore this.
This commit is contained in:
Christian Brueffer 2004-06-18 18:50:50 +00:00
parent 3848871f1e
commit b4212d03a1
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=21187
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1598,23 +1598,23 @@ Success, response: OK, Success (0x20)</screen>
<sect2>
<title>Serial Port (SP) Profile</title>
<para>The Serial Port (SP) profile allows Bluetooth device to perform
<para>The Serial Port (SP) profile allows Bluetooth devices to perform
RS232 (or similar) serial cable emulation. The scenario covered by this
profile deals with legacy applications using Bluetooth as a cable
replacement, through a virtual serial port abstraction.</para>
<para>The &man.rfcomm.sppd.1; utility implements the Serial Port profile.
Pseudo tty is used as a virtual serial port abstraction. The example
A pseudo tty is used as a virtual serial port abstraction. The example
below shows how to connect to a remote device Serial Port service.
Note that you do not have to specify RFCOMM channel -
Note that you do not have to specify a RFCOMM channel -
&man.rfcomm.sppd.1; can obtain it from the remote device via SDP.
If you would like to override this, specify RFCOMM channel in the
If you would like to override this, specify a RFCOMM channel on the
command line.</para>
<screen>&prompt.root; <userinput>rfcomm_sppd -a 00:07:E0:00:0B:CA -t /dev/ttyp6</userinput>
rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<para>Once connected pseudo tty can be used as serial port.</para>
<para>Once connected, the pseudo tty can be used as serial port.</para>
<screen>&prompt.root; <userinput>cu -l ttyp6</userinput></screen>
@ -1627,8 +1627,8 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<title>A remote device cannot connect</title>
<para>Some older Bluetooth devices do not support role switching.
By default, when &os; is accepting a new connection, it tries to
perform role switch and become a master. Devices, which do not
support this will not be able to connect. Note the role switching is
perform a role switch and become master. Devices, which do not
support this will not be able to connect. Note that role switching is
performed when a new connection is being established, so it is not
possible to ask the remote device if it does support role switching.
There is a HCI option to disable role switching on the local