After bluez compilation it says: If you need init scripts for the other daemons, please file requests https://bugs.gentoo.org So, there is need for dund daemon to be launched. It would be nice to have options in /etc/conf.d/bluetooth like: DUND_ENABLE=true DUND_OPTIONS="--listen --persist --msdun --channel 1 call dun" Also, it would be nise that dund be triggered by udev/dbus rules, e.g. only on bluetooth dongle plug in. Reproducible: Always
Why do you still need this old daemon? It should be deprecated by the new Service framework... Thanks
(In reply to comment #1) I do need it to connect my palm via bluetooth via DUND and pppd. Currently it is impossible (or I don't know how to do) it. A spend googling a few days, but found not the answer. If you know how to launch pppd on incoming connection from palm (as dund does), I will be thankfull.
Sadly I don't know how to do that :-(, have you tried to ask for help in bluez-users IRC channel? http://www.bluez.org/contact/
(In reply to comment #3) Thanks for counsel. I have asked in bluez community mail list (http://marc.info/?l=linux-bluetooth&m=128441070517009&w=2) and they recommended only partial solution for sync'ing but not DUNd successor. :( So, there is steel need to launch dund on BT-dongle plug.
OK, I am also subscribed to bluez mailing list and followed that thread ;-) I will try to prepare init.d and conf.d files for that, but, of course, if you have some partial work already done, feel free to attach it here :-D Thanks
+*bluez-4.72 (24 Sep 2010) + + 24 Sep 2010; Pacho Ramos <pacho@gentoo.org> -bluez-4.70.ebuild, + +bluez-4.72.ebuild, +files/conf.d-dund, +files/init.d-dund, metadata.xml: + Version bump with multiple fixes and initial support for HDP plugin, mcap + plugin configure option was dropped as it is enabled when needed at + runtime. Provide a dund init script as demanded by DMoL in bug #328847. + Remove old. +
