From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: bluetooth-guide.xml
Date: Thu, 16 Jul 2009 23:02:02 +0000 [thread overview]
Message-ID: <E1MRZxi-0000CA-0a@stork.gentoo.org> (raw)
nightmorph 09/07/16 23:02:02
Modified: bluetooth-guide.xml
Log:
updated bluetooth guide, emergency fixes, bug 266690. we now no longer have a chapter on setting up a PAN, since nobody knows how the hell to do this.
Revision Changes Path
1.16 xml/htdocs/doc/en/bluetooth-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?r1=1.15&r2=1.16
Index: bluetooth-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- bluetooth-guide.xml 22 Oct 2007 05:28:14 -0000 1.15
+++ bluetooth-guide.xml 16 Jul 2009 23:02:01 -0000 1.16
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.15 2007/10/22 05:28:14 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.16 2009/07/16 23:02:01 nightmorph Exp $ -->
<guide link="/doc/en/bluetooth-guide.xml">
<title>Gentoo Linux Bluetooth Guide</title>
@@ -20,6 +20,9 @@
<author title="Editor">
<mail link="rane@gentoo.org">Łukasz Damentko</mail>
</author>
+<author title="Editor">
+ <mail link="nightmorph"/>
+</author>
<abstract>
This guide will explain how to successfully install a host Bluetooth device,
@@ -31,8 +34,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.10</version>
-<date>2007-10-21</date>
+<version>1.11</version>
+<date>2009-07-16</date>
<chapter id="introduction">
<title>Introduction</title>
@@ -55,17 +58,15 @@
<body>
<p>
-The first part of this guide is to identify qualified and non-qualified devices
-that support the Bluetooth technology. This way, users can purchase Bluetooth
-devices that are known to work. After that, the guide explains how to configure
-the system kernel, identify the Bluetooth devices installed on the system and
-detected by the kernel and install the necessary basic Bluetooth tools.
+The first part of this guide explains how to configure the system kernel,
+identify the Bluetooth devices installed on the system and detected by the
+kernel and install the necessary basic Bluetooth tools.
</p>
<p>
The second part covers how to detect remote devices and how to establish a
connection from or to them by either setting up radio frequency communication
-(RFCOMM) or by setting up a personal area network (PAN).
+(RFCOMM)<!-- or by setting up a personal area network (PAN)-->.
</p>
<p>
@@ -77,27 +78,6 @@
</section>
</chapter>
-<chapter id="devices">
-<title>Supported Devices</title>
-<section>
-<title>Qualified and non-qualified devices that support Bluetooth</title>
-<body>
-
-<impo>
-These products might work even though some are not qualified Bluetooth
-products. Gentoo does not support them in any way, they might just work.
-</impo>
-
-<p>
-A list of the currently supported devices can be found at: <uri
-link="http://www.holtmann.org/linux/bluetooth/features.html">Bluetooth device
-features and revision information by Marcel Holtmann</uri>.
-</p>
-
-</body>
-</section>
-</chapter>
-
<chapter id="kernel">
<title>Configuring the system</title>
<section>
@@ -108,7 +88,7 @@
As the latest Linux stable kernel is 2.6, the configuration will be done for
these series of the kernel. Most Bluetooth devices are connected to a USB port,
so USB will be enabled too. Please refer to the <uri
-link="/doc/en/usb-guide.xml"> Gentoo Linux USB Guide</uri>.
+link="/doc/en/usb-guide.xml">Gentoo Linux USB Guide</uri>.
</p>
<pre caption="Configuration for 2.6 kernels">
@@ -312,14 +292,6 @@
</impo>
<note>
-If you are using <c><=bluez-libs-2.x</c> and <c><=bluez-utils-2.x</c> you
-can choose from different pin helpers, depending on what you want to use.
-Available pin helpers are: <c>/usr/lib/kdebluetooth/kbluepin</c>
-(net-wireless/kdebluetooth), <c>/usr/bin/bluepin</c> or
-<c>/etc/bluetooth/pin-helper</c> among others.
-</note>
-
-<note>
Beginning with <c>>=bluez-libs-3.x</c> and <c>>=bluez-utils-3.x</c>, pin helpers
have been replaced by passkey agents. There are a few different graphical
passkey agents available to help manage your PIN, such as <c>bluez-gnome</c> and
@@ -523,92 +495,7 @@
</body>
</section>
-<section>
-<title>Setting up a Personal Area Network (PAN)</title>
-<body>
-
-<note>
-Please note that setting up a Personal Area Network is optional. This section
-describes how to set up and connect to a Network Access Point, though setting
-up a Group Ad-Hoc Network follows a similar way.
-</note>
-
-<p>
-First of all, we need the <c>bnep</c> module loaded. And probably we want it
-loaded each time the computer starts.
-</p>
-
-<pre caption="Loading the bnep module">
-# <i>modprobe bnep</i>
-# <i>echo "bnep" >> /etc/modules.autoload.d/kernel-2.6</i>
-</pre>
-
-<p>
-We have to start the <c>pand</c> daemon in the host that will provide the NAP.
-We'll have to specify that we want to provide a NAP service and that this host
-will be the master, thus the other hosts that connect to it, the slaves.
-Another possible service is GN (Group ad-hoc Network).
-</p>
-
-<pre caption="Running the pand daemon">
-# <i>pand --listen --role NAP --master --autozap</i>
-</pre>
-
-<p>
-After doing that, we have a host listening, so the rest of hosts just have to
-connect to that one.
-</p>
-
-<pre caption="Connecting to the Network Access Point">
-# <i>pand --connect 00:0A:0B:0C:0D:0E --service NAP --autozap</i>
-</pre>
-
-<p>
-If everything went fine, we can now configure the IP addresses of our hosts.
-</p>
-
-<pre caption="bnep IP address configuration">
-host0 #<i> ifconfig bnep0 192.168.2.1</i>
-host1 #<i> ifconfig bnep0 192.168.2.2</i>
-
-host0 #<i> ifconfig bnep0</i>
-bnep0 Link encap:Ethernet HWaddr 00:0A:0B:0C:0D:0E
- inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
- inet6 addr: fe80::210:60ff:fea3:cb41/64 Scope:Link
- UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
- RX packets:0 errors:0 dropped:0 overruns:0 frame:0
- TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
- collisions:0 txqueuelen:1000
- RX bytes:208 (208.0 b) TX bytes:188 (188.0 b)
-
-host1 #<i> ifconfig bnep0</i>
-bnep0 Link encap:Ethernet HWaddr 00:01:02:03:04:05
- inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
- inet6 addr: fe80::210:60ff:fea2:dd2a/64 Scope:Link
- UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
- RX packets:0 errors:0 dropped:0 overruns:0 frame:0
- TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
- collisions:0 txqueuelen:1000
- RX bytes:208 (208.0 b) TX bytes:188 (188.0 b)
-</pre>
-
-<p>
-Finally, we can do a simple test to see that the network is working fine.
-</p>
-
-<pre caption="IP ping between bnep interfaces">
-host1 #<i> ping 192.168.2.1</i>
-PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
-64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.0 ms
-64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=37.3 ms
-
---- 192.168.2.1 ping statistics ---
-2 packets transmitted, 2 received, 0% packet loss, time 1000ms
-rtt min/avg/max/mdev = 34.045/35.690/37.336/1.656 ms
-</pre>
-
-</body>
-</section>
+<!-- Deleting pan chapter, bug 266690, until we know how the hell to do this -->
</chapter>
<chapter id="apps">
next reply other threads:[~2009-07-16 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 23:02 Joshua Saddler (nightmorph) [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-21 19:03 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: bluetooth-guide.xml Joshua Saddler (nightmorph)
2012-06-29 19:09 Sven Vermeulen (swift)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1MRZxi-0000CA-0a@stork.gentoo.org \
--to=nightmorph@gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox