From: Andrew Kohlsmith <akohlsmith-bluez@benshaw.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] What happened with pin_helper (hcid.conf)?
Date: Wed, 10 Jan 2007 12:12:51 -0500 [thread overview]
Message-ID: <200701101212.51800.akohlsmith-bluez@benshaw.com> (raw)
In-Reply-To: <1A3C202B-4795-4352-8B71-26F102A84F2E@gmail.com>
On Wednesday 10 January 2007 11:56 am, Bas Schulte wrote:
> hcid complains when I do just that:
>
> Jan 10 17:56:27 localhost hcid[8326]: Unknown option 'pin_helper'
> line 26
I just use "passkey 0000;" and security auto. It seems to be the New Way if
you don't want to use dbus.
-A.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-01-10 17:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 16:05 [Bluez-users] What happened with pin_helper (hcid.conf)? Bas Schulte
2007-01-10 16:12 ` Brad Midgley
2007-01-10 16:31 ` Bas Schulte
2007-01-10 16:51 ` Brad Midgley
2007-01-10 16:56 ` Bas Schulte
2007-01-10 17:12 ` Andrew Kohlsmith [this message]
2007-01-10 17:54 ` Bas Schulte
2007-01-10 17:04 ` Bas Schulte
2007-01-10 17:13 ` Paul Gardiner
2007-01-10 17:28 ` Bas Schulte
2007-01-10 17:41 ` Marcel Holtmann
2007-01-10 17:56 ` Bas Schulte
2007-01-10 18:00 ` Marcel Holtmann
2007-01-10 18:07 ` Bas Schulte
2007-01-10 18:38 ` David Armour
2007-01-10 18:39 ` Bearcat M. Sandor
2007-01-10 18:56 ` Bas Schulte
2007-01-11 10:03 ` Stefan Seyfried
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=200701101212.51800.akohlsmith-bluez@benshaw.com \
--to=akohlsmith-bluez@benshaw.com \
--cc=bluez-users@lists.sourceforge.net \
/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