public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bearcat M. Sandor" <linux@feline-soul.com>
To: "Marcel Holtmann" <marcel@holtmann.org>
Cc: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] How do I reset a pairing?
Date: Tue, 29 Aug 2006 15:32:31 -0600 (MDT)	[thread overview]
Message-ID: <2461.216.47.59.131.1156887151.squirrel@webmail.feline-soul.net> (raw)
In-Reply-To: <1156892459.4026.56.camel@aeonflux.holtmann.net>

Marcel,

I looked it over. I am only just starting to learn C so this is a little
daunting. I tried a "gcc -Wall -o passkey-agent -passkey-agent.c" and that
didn't work (i didn't really expect it to). I didn't see a configure
script that would create a make file for the agent.

If my X system goes down, all of my paring  devices will go down with it,
since i would need gnome up to get them working. How can i get this agent
working?

I'm just confused. Since the bluez-gnome is a new release, what did people
do before it arrived to get pairing devices working?

Thank you for the help so far. I appreciate your time.

Bearcat

> Hi Bearcat,
>
>> I've looked through the blues-utils 3.2 source code directories and not
>> seen such a script. Can you point it out to me, or is it code that need
>> to
>> be compiled, or a pice of code that needs to be extracted/followed.
>
> it is hcid/passkey-agent.c and it is a C program. You can of course do
> the same in Python or any other language with D-Bus bindings.
>
> Regards
>
> Marcel
>
>
>

  reply	other threads:[~2006-08-29 21:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  8:29 [Bluez-users] How do I reset a pairing? jonny Linux
2006-08-27 12:18 ` jonny Linux
2006-08-28 12:17   ` Claudio Takahasi
2006-08-28 16:30     ` jonny Linux
2006-08-28 18:14       ` Claudio Takahasi
2006-08-28 18:45         ` Bearcat M. Sandor
2006-08-28 21:15           ` Marcel Holtmann
2006-08-28 19:39             ` Bearcat M. Sandor
2006-08-28 23:54               ` Marcel Holtmann
2006-08-28 22:24                 ` Bearcat M. Sandor
2006-08-29 10:47                   ` Marcel Holtmann
2006-08-29 17:03                     ` jonny Linux
2006-08-29 20:34                     ` Bearcat M. Sandor
2006-08-29 22:35                       ` Marcel Holtmann
2006-08-29 20:52                         ` Bearcat M. Sandor
2006-08-29 23:00                           ` Marcel Holtmann
2006-08-29 21:32                             ` Bearcat M. Sandor [this message]
2006-08-29 23:46                               ` Marcel Holtmann
2006-08-29 22:05                                 ` Bearcat M. Sandor
2006-08-30  1:08                                 ` Bearcat M. Sandor
2006-08-30  3:30                                   ` manojt ambe
2006-08-30  9:52                                   ` Marcel Holtmann
2006-08-31  2:48                                     ` Bearcat M. Sandor
2006-08-31 11:04                                       ` Marcel Holtmann
2006-08-31 17:50                                         ` Bearcat M. Sandor
2006-08-31 22:08                                           ` Marcel Holtmann
2006-09-01  0:29                                             ` Bearcat M. Sandor
2006-09-01 11:04                                               ` Marcel Holtmann

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=2461.216.47.59.131.1156887151.squirrel@webmail.feline-soul.net \
    --to=linux@feline-soul.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.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