From: "Collin R. Mulliner" <collin@betaversion.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bluetooth filesystem integration
Date: Wed, 28 Sep 2005 22:27:14 -0700 [thread overview]
Message-ID: <1127971635.24702.7.camel@panic> (raw)
In-Reply-To: <1127896508.5321.3.camel@localhost.localdomain>
> hink is need and useful.
>
> please also post ideas on the directory layout. How we handle multiple
> local devices and the remote devices.
so the original filesystem layout was:
/CFG/
/CFG/inquiry_duration
/CFG/cache_time
/CFG/SCAN_NOW
just the config
/OPUSH/
/OPUSH/CollinsPhone
/OPUSH/myPalm
holds names of all devices which publish a OPUSH service record
cp <somefile> /OPUSH/myPalm (would start OPUSH to the device)
/DEVICES/
/DEVICES/00:12:34:56:78
/DEVICES/00:AB:CD:EF:AA
/DEVICES/00:1A:2B:3C:4D
just bd_addrs of all visible devices
I the future I also want to have a directory to represent device and
service classes (e.g. all printers).
And even more information about a device, like feature list or
manufacturer etc.. This should go somewhere like /DEVICES/bd_addr/info
... Collin
--
Collin R. Mulliner <collin@betaversion.net>
BETAVERSiON Systems [www.betaversion.net]
info/pgp: finger collin@betaversion.net
All programmers are optimists --Frederick P. Brooks, Jr.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-09-29 5:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 23:52 [Bluez-devel] bluetooth filesystem integration Collin R. Mulliner
2005-09-28 8:35 ` Marcel Holtmann
2005-09-29 5:27 ` Collin R. Mulliner [this message]
2005-09-28 9:21 ` Charles Bueche
2005-09-28 9:32 ` Marcel Holtmann
2005-09-28 11:19 ` Charles Bueche
2005-09-28 14:42 ` Bastien Nocera
2005-09-28 18:16 ` Dimitry Andric
2005-09-29 16:45 ` 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=1127971635.24702.7.camel@panic \
--to=collin@betaversion.net \
--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