From: Marcel Holtmann <marcel@holtmann.org>
To: Matthias Thomae <bluez@thomae-privat.de>
Cc: Edd Dumbill <edd@usefulinc.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] starting order in debian init script for bluez
Date: Sun, 11 Jul 2004 17:22:42 +0200 [thread overview]
Message-ID: <1089559362.24919.7.camel@pegasus> (raw)
In-Reply-To: <40F11592.8090704@thomae-privat.de>
Hi Matthias,
> So it would still make sense to call hci2hid before rfcomm/dund/pand,
> wouldn't it?
this depends on what you wanna do, but you should make sure that at
least hcid and sdpd are running.
> BTW, this is exactly the case in the init script contained in
> bluez-utils 2.8:
I know, because I wrote that init script. If you don't like the Debian
init script or thing it is wrong, file a bug report for it.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-07-11 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 18:27 [Bluez-devel] starting order in debian init script for bluez Matthias Thomae
2004-07-10 18:55 ` Marcel Holtmann
2004-07-11 10:25 ` Matthias Thomae
2004-07-11 15:22 ` Marcel Holtmann [this message]
2004-07-11 15:27 ` Matthias Thomae
2004-07-11 17:17 ` Edd Dumbill
2004-07-11 19:32 ` Matthias Thomae
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=1089559362.24919.7.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez@thomae-privat.de \
--cc=edd@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