From: Sebastian Roth <sebiroth@web.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: USB Bluetooth works manually, but won't hotplug with the SAME script
Date: Sun, 20 Feb 2005 17:45:48 +0100 [thread overview]
Message-ID: <cvael0$d6q$1@sea.gmane.org> (raw)
In-Reply-To: <20050219182455.68861.qmail@web53009.mail.yahoo.com>
Hi Alfredo,
I can't say what exactly the problem is but IMHO the script
is not structured very wise. Maybe the script is executed before
the needed modules are loaded when used for hotplugging.
Here is my suggestion for a script:
#!/bin/sh
# get the bluetooth things ready
PATH=/bin:/sbin:/usr/bin:/usr/sbin
# load all modules
modprobe bluetooth
modprobe hci_usb
modprobe l2cap
modprobe rfcomm
# start the deamons
# AFAIK the configfile paths are default
# so there is no need to specify these
hcid
sdpd
rfcomm bind all
# this is done by hcid!
# hciconfig hci0 up
# don't really know what these
# commands do but seems ok to me
sdptool add --channel=3 SP
dund --listen --channel 3 --msdun noauth
:192.168.1.240 crtscts 115200 ms-dns 192.168.1.1 lock
I have not tested this script but it _should_ work.
Best regards,
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-20 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 18:24 [Bluez-users] USB Bluetooth works manually, but won't hotplug with the SAME script Alfredo Meraz
2005-02-20 16:45 ` Sebastian Roth [this message]
2005-02-21 18:50 ` [Bluez-users] " Alfredo Meraz
2005-02-21 23:02 ` 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='cvael0$d6q$1@sea.gmane.org' \
--to=sebiroth@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.