From: Josh Saddler <nightmorph@stork.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: bluetooth-guide.xml
Date: Wed, 16 May 2007 09:10:33 +0000 [thread overview]
Message-ID: <E1HoFWj-0004hc-6s@stork.gentoo.org> (raw)
nightmorph 07/05/16 09:10:33
Modified: bluetooth-guide.xml
Log:
added stuff on the upcoming 3.x PIN stuff, bug 178100
Revision Changes Path
1.13 xml/htdocs/doc/en/bluetooth-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?rev=1.13&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?rev=1.13&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml?r1=1.12&r2=1.13
Index: bluetooth-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- bluetooth-guide.xml 10 Apr 2007 06:48:59 -0000 1.12
+++ bluetooth-guide.xml 16 May 2007 09:10:33 -0000 1.13
@@ -1,7 +1,7 @@
<?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.12 2007/04/10 06:48:59 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.13 2007/05/16 09:10:33 nightmorph Exp $ -->
<guide link="/doc/en/bluetooth-guide.xml">
<title>Gentoo Linux Bluetooth Guide</title>
@@ -32,8 +32,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.8</version>
-<date>2007-04-09</date>
+<version>1.9</version>
+<date>2007-05-16</date>
<chapter id="introduction">
<title>Introduction</title>
@@ -266,7 +266,8 @@
# Pairing mode
pairing multi;
-<comment>(Change pin_helper to use /etc/bluetooth/pin-helper)</comment>
+<comment>(You only need a pin helper if you are using <=bluez-libs-2.x and <=bluez-utils-2.x)
+(Change pin_helper to use /etc/bluetooth/pin-helper)</comment>
# PIN helper
pin_helper /etc/bluetooth/pin-helper;
}
@@ -303,15 +304,8 @@
pairing this device with another one.
</p>
-<note>
-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>
-
<pre caption="Editing /etc/bluetooth/pin">
-<comment>(Change 123456 with your desired pin number.)</comment>
+<comment>(Replace 123456 with your desired pin number.)</comment>
123456
</pre>
@@ -322,6 +316,22 @@
devices.
</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
+<c>kdebluetooth</c>. You can also use <c>passkey-agent</c> (found in
+<c>bluez-utils</c>) from the command line.
+</note>
+
</body>
</section>
<section>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2007-05-16 9:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 9:10 Josh Saddler [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-22 5:28 [gentoo-doc-cvs] cvs commit: bluetooth-guide.xml Josh Saddler
2007-10-22 5:27 Josh Saddler
2007-01-14 12:36 Josh Saddler
2006-11-27 0:16 Josh Saddler
2006-11-02 18:37 Josh Saddler
2006-09-19 10:24 Jan Kundrat
2006-03-02 23:59 Xavier Neys
2006-01-05 19:57 swift
2005-09-07 0:27 Jose Luis Rivero
2005-08-31 15:03 Xavier Neys
2005-08-27 9:19 swift
2005-08-25 10:43 Shyam Mani
2005-08-25 7:06 Shyam Mani
2005-08-22 6:59 Shyam Mani
2005-08-15 23:16 Camille Huot
2005-07-28 12:20 Shyam Mani
2005-07-26 11:44 Shyam Mani
2005-07-25 11:12 Shyam Mani
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=E1HoFWj-0004hc-6s@stork.gentoo.org \
--to=nightmorph@stork.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