From: Fredrik Noring <noring@nocrew.org>
To: "Fred Schättgen" <bluez-devel@schaettgen.de>
Cc: GNOME Bluetooth Mailing List <gnome-bluetooth@usefulinc.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [gnome-bluetooth] Re: [Bluez-devel] What stuff in gnome-bluetooth does, and ideas for its future
Date: Fri, 30 Jan 2004 19:10:42 +0100 [thread overview]
Message-ID: <1075486241.14644.34.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <200401292119.45926.bluez-devel@schaettgen.de>
tor 2004-01-29 klockan 21.19 skrev Fred Sch=E4ttgen:
> I also think that wouldn't be misplaced in bluez. But since it can be e=
asily=20
> done with a gnome/kde service, this proposal will surely go to the bott=
om=20
> part of the wishlist if there is no demand from other unrelated project=
s.=20
Here's a proposal:
Similar to the idea with /etc/bluetooth/keytab.socket, additional
sockets can be created for other Bluetooth interface services such
as name scans, lookups etc. Regular users have access to these
capabilities based on socket file permissions.
Example:
/etc/bluetooth/names # The device name cache
/etc/bluetooth/names.conf # The device name configuration file
/etc/bluetooth/names.socket # The command socket
Command examples:
SCAN - Returns something similar to "hcitool scan"
LOOKUP <bdaddr> - Returns the name if available in the names file
DELETE <bdaddr> - Removes the name from the names file
LIST - Lists all names in the names file
The hcitool utility can be extended with these features too.
Would this make it?
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-30 18:10 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
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 ` Fredrik Noring [this message]
2004-01-30 18:26 ` [gnome-bluetooth] " 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=1075486241.14644.34.camel@akka.yeti.nocrew.org \
--to=noring@nocrew.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-devel@schaettgen.de \
--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