From: Paul Hedderly <bulkpaul@mjr.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] link_key editor
Date: Mon, 20 Sep 2004 11:21:51 +0100 [thread overview]
Message-ID: <20040920102151.GT26469@wacka.mjr.org> (raw)
Well I think the subject says it all. Is there (preferably command line)
a link_key editor? I'd like to be able to list the keys and remove them
individually for when I'm playing with stuff.
--
Cheers
Paul
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-09-20 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 10:21 Paul Hedderly [this message]
2004-09-20 10:32 ` [Bluez-devel] link_key editor Marcel Holtmann
[not found] ` <20040920104619.GV26469@wacka.mjr.org>
2004-09-20 15:53 ` 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=20040920102151.GT26469@wacka.mjr.org \
--to=bulkpaul@mjr.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