From: Dave Mielke <dave@mielke.cc>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] PIN helper
Date: Thu, 9 Mar 2006 01:12:55 -0500 [thread overview]
Message-ID: <20060309061255.GC4516@beta.private.mielke.cc> (raw)
In-Reply-To: <20060309070649.007fba22.fotopiper@o2.pl>
[quoted lines by Radek Rurarz on 2006/03/09 at 07:06 +0100]
>A simpler method would be to relly on another pinhelper (for
>instance one from the bluez-utlis) set in a config file.. juts pass the
>arguments to it.. and see if it returns a propper pin.. if not fall
>back to the internal methods (promp if allowed, the pin file shoud be
>checked first).
Do you think it should be just one, or should multiple specifications of the
option accumulate a set of helpers to try?
>Sorry, didn't noticed that... I need to work on my sh skills ;)
I'm grateful that you didn't as that gave me the idea to document the
"feature".
--
Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me
EMail: dave@mielke.cc | Canada K2A 1H7 | if you're concerned about Hell.
http://FamilyRadio.com/ | http://Mielke.cc/bible/
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-03-09 6:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 21:19 [Bluez-devel] PIN helper Radek
2006-03-08 21:40 ` Dave Mielke
2006-03-08 22:01 ` Radek Rurarz
2006-03-08 22:16 ` Dave Mielke
2006-03-09 5:44 ` Radek Rurarz
2006-03-09 5:55 ` Dave Mielke
2006-03-09 6:06 ` Radek Rurarz
2006-03-09 6:12 ` Dave Mielke [this message]
2006-03-09 18:29 ` Radek Rurarz
2006-03-09 19:34 ` Dave Mielke
2006-03-09 21:55 ` Radek Rurarz
2006-03-09 22:04 ` Radek Rurarz
2006-03-10 1:33 ` Dave Mielke
2006-03-10 7:28 ` Radek Rurarz
2006-03-10 13:35 ` Dave Mielke
2006-03-10 18:10 ` Radek Rurarz
2006-03-10 17:25 ` Dave Mielke
2006-03-10 18:13 ` Radek Rurarz
2006-03-10 18:39 ` Dave Mielke
2006-03-10 19:22 ` Radek Rurarz
2006-03-10 20:55 ` Dave Mielke
2006-03-10 22:24 ` Radek Rurarz
2006-03-10 23:04 ` Dave Mielke
2006-03-13 4:08 ` KrAnTi KaMbHaMpAtI
2006-03-10 20:56 ` Dave Mielke
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=20060309061255.GC4516@beta.private.mielke.cc \
--to=dave@mielke.cc \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).