From: Marcel Holtmann <marcel@holtmann.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Nicholas A. Preyss" <nalp@gmx.net>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-utils 2.7 default configuration
Date: Wed, 12 May 2004 19:20:45 +0200 [thread overview]
Message-ID: <1084382445.25099.77.camel@pegasus> (raw)
In-Reply-To: <1084371486.4426.156.camel@hades.cambridge.redhat.com>
Hi David,
> > the bluez-utils-2.7 now contains sdpd, pand, dund and hidd. So there was
> > a need for a new init script that is able to start each of these daemons
> > on bootup. I enabled hidd by default, because it didn't harm if it is
> > started and hid2hci makes also sense. Why should it not be started?
>
> For the Fedora package I've put pand, dund and hidd in separate init
> scripts. It's expected that individual services can be enabled or
> disabled with chkconfig or system-config-services, rather than by
> manually editing a separate config file.
>
> Also, I've often been glad of being able to restart pand _separately_
> from hcid and sdpd. Doesn't sdpd forget _everything_ that's registered
> when you restart it?
>
> But hid2hci does make sense, assuming of course that you're not relying
> on a Bluetooth HID device without having the Linux BT-HID support
> working yet.
I have no problem with that, but for the upstream package I am going to
keep it this way. If you aren't a developer then you start the daemons
at boot and kill them at shutdown. That's all.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-12 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 19:29 [Bluez-devel] bluez-utils 2.7 default configuration Nicholas A. Preyss
2004-05-12 13:23 ` Marcel Holtmann
2004-05-12 14:18 ` David Woodhouse
2004-05-12 17:20 ` Marcel Holtmann [this message]
2004-05-12 17:25 ` David Woodhouse
2004-05-12 17:29 ` Marcel Holtmann
2004-05-12 17:33 ` David Woodhouse
2004-05-12 17:45 ` Marcel Holtmann
2004-05-12 17:56 ` David Woodhouse
2004-05-12 21:50 ` Marcel Holtmann
2004-05-20 9:15 ` David Woodhouse
2004-05-20 9:20 ` Marcel Holtmann
2004-05-20 9:28 ` David Woodhouse
2004-05-20 9:42 ` Marcel Holtmann
2004-05-20 22:04 ` billy pucyutan
2004-05-30 17:20 ` David Woodhouse
2004-05-31 22:22 ` Marcel Holtmann
2004-05-31 22:43 ` David Woodhouse
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=1084382445.25099.77.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
--cc=nalp@gmx.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