From: Mitja Pufic <raveer@section-one.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Support for stored link keys
Date: Thu, 21 Apr 2005 18:37:34 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0504211835330.16740@cherokee.spacecom.si> (raw)
In-Reply-To: <1114099644.32265.31.camel@pegasus>
Hello again,
> I don't know for what this is needed. The current hcid stores the link
> keys now under /var/lib/bluetooth and it uses a subdirectory with the
> text representation of the BD_ADDR to differ between adapters.
Dissregard the previous question :) I will install 2.16 and shut up for
now :) I see that each device has its own subdirectory.
thanks and regards,
mitja
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-21 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 14:46 [Bluez-devel] Support for stored link keys Marcel Holtmann
2005-04-21 15:55 ` Mitja Pufic
2005-04-21 16:07 ` Marcel Holtmann
2005-04-21 16:34 ` Mitja Pufic
2005-04-21 16:45 ` Marcel Holtmann
2005-04-22 22:26 ` Scott W Gifford
2005-04-22 22:55 ` Henryk Plötz
2005-04-23 0:00 ` Marcel Holtmann
2005-04-24 18:12 ` Fred Schaettgen
2005-04-21 16:37 ` Mitja Pufic [this message]
2005-04-28 18:28 ` David Woodhouse
2005-04-29 9:37 ` 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=Pine.LNX.4.61.0504211835330.16740@cherokee.spacecom.si \
--to=raveer@section-one.org \
--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