From: Fredrik Noring <noring@nocrew.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: GNOME Bluetooth Mailing List <gnome-bluetooth@usefulinc.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [gnome-bluetooth] What stuff in gnome-bluetooth does, and ideas for its future
Date: Thu, 29 Jan 2004 01:50:41 +0100 [thread overview]
Message-ID: <1075337441.553.97.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <1075331039.553.80.camel@akka.yeti.nocrew.org>
Hi
> An ascii version could be row based. What about like this?
>
> 00:11:22:33:44:55 66:77:88:99:00:11 6d450822cf944dcedd7a5b2e347e606f key_type 1075330902
What about replacing /etc/bluetooth/link_key with an ASCII version in
/etc/bluetooth/keytab? I'll work on a patch for it..
I'm also thinking about the possibility of making a device name cache
in /etc/bluetooth/names, somewhat similar to /etc/hosts. And so whenever
someone requests a scan this table can be updated:
# /etc/bluetooth/names
#
# Bluetooth address Last updated Device name
00:11:22:33:44:55 1075337039 Some Bluetooth device name
66:77:88:99:00:11 1075337039 Some other Bluetooth device name
The configuration for this service can for example be located in
/etc/bluetooth/names.conf.
Having a device name cache makes it a lot easier to display the names
associated with the addresses in the /etc/bluetooth/keytab file.
Comments?
Fredrik
_______________________________________________
gnome-bluetooth mailing list
gnome-bluetooth@usefulinc.com
http://lists.usefulinc.com/mailman/listinfo/gnome-bluetooth
next prev parent reply other threads:[~2004-01-29 0:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1064593223.12843.127.camel@saag>
[not found] ` <1067882864.15593.326.camel@dhcp-116.surrey.redhat.com>
[not found] ` <1067906859.15607.48.camel@saag>
2004-01-28 23:04 ` [gnome-bluetooth] What stuff in gnome-bluetooth does, and ideas for its future Fredrik Noring
2004-01-29 0:50 ` Fredrik Noring [this message]
2004-01-29 11:09 ` Edd Dumbill
2004-01-29 15:22 ` Marcel Holtmann
2004-01-29 15:32 ` Edd Dumbill
2004-01-29 18:14 ` Fredrik Noring
2004-01-30 17:45 ` Fredrik Noring
2004-01-30 18:18 ` Marcel Holtmann
2004-01-30 20:31 ` Fredrik Noring
2004-01-29 11:30 ` [Bluez-devel] " Fred Schättgen
2004-01-29 18:44 ` Fredrik Noring
2004-01-29 20:19 ` [Bluez-devel] " Fred Schättgen
2004-01-30 18:10 ` [gnome-bluetooth] " Fredrik Noring
2004-01-30 18:26 ` Marcel Holtmann
2004-01-30 18:49 ` Eugene Crosser
2004-01-30 19:06 ` Marcel Holtmann
2004-01-30 20:41 ` Fredrik Noring
2004-01-30 20:35 ` Fredrik Noring
2004-01-30 18:49 ` [Bluez-devel] name cache Fred Schättgen
2004-01-30 20:54 ` Fredrik Noring
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=1075337441.553.97.camel@akka.yeti.nocrew.org \
--to=noring@nocrew.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=edd@usefulinc.com \
--cc=gnome-bluetooth@usefulinc.com \
/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