From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] "hcitool dev" shows no devices
Date: Sun, 30 Jan 2005 22:11:06 +0100 [thread overview]
Message-ID: <41FD4D6A.9000107@gmx.ch> (raw)
In-Reply-To: <1107118082.8384.10.camel@pegasus>
Hello Marcel
Marcel Holtmann wrote:
> Hi Marco,
>
>
>>But another question arised starting hcid:
>>The location of etc/bluetooth/pin. Is it hardcoded?
>>I crosscompiled the bluez libs/utils and hcid now tells me on start:
>>Can't open PIN file /usr/local/arm/2.95.3/arm-linux/etc/bluetooth/pin. No
>>such file or directory(2)
>>
>>Can I change the location of the pin-file? maybee in the hcid.conf?
>
>
> there is no option for that. However you can provide a patch if you
> think such an option is usefull.
>
> You forgot "--sysconfdir=/etc" when you call configure as it is written
> in the README.
that does exactly what I need (and my c knowledge is very limited, I'd
require a couple of weeks for a patch :-))!
thanks a lot for your help!
kind regards
Marco
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-01-30 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 20:05 [Bluez-users] "hcitool dev" shows no devices Marco Trudel
2005-01-30 20:15 ` Marcel Holtmann
2005-01-30 20:40 ` Marco Trudel
2005-01-30 20:48 ` Marcel Holtmann
2005-01-30 21:11 ` Marco Trudel [this message]
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=41FD4D6A.9000107@gmx.ch \
--to=mtrudel@gmx.ch \
--cc=bluez-users@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