SHA256
1
0
forked from pool/bluez
Go to file
Stefan Seyfried 379ddb662f Accepting request 22246 from home:seife:testing
Copy from home:seife:testing/bluez via accept of submit request 22246 revision 33.
Request was accepted with message:
update to bluez-4.56

OBS-URL: https://build.opensuse.org/request/show/22246
OBS-URL: https://build.opensuse.org/package/show/Base:System/bluez?expand=0&rev=25
2009-10-12 06:19:56 +00:00
.gitattributes OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=1 2008-09-15 08:31:24 +00:00
.gitignore OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=1 2008-09-15 08:31:24 +00:00
bluetooth.modprobe OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=20 2009-01-13 17:37:58 +00:00
bluetooth.sh Accepting request 21664 from home:seife:testing 2009-10-04 21:07:30 +00:00
bluetooth.sysconfig OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=38 2009-07-10 14:41:47 +00:00
bluez-4.44-udev-use-helperscript.diff OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=38 2009-07-10 14:41:47 +00:00
bluez-4.56.tar.bz2 Accepting request 22246 from home:seife:testing 2009-10-12 06:19:56 +00:00
bluez-coldplug.init Accepting request 18609 from Base:System 2009-08-27 17:11:24 +00:00
bluez-gstreamer.changes Accepting request 22246 from home:seife:testing 2009-10-12 06:19:56 +00:00
bluez-gstreamer.spec Accepting request 22246 from home:seife:testing 2009-10-12 06:19:56 +00:00
bluez.changes Accepting request 22246 from home:seife:testing 2009-10-12 06:19:56 +00:00
bluez.spec Accepting request 22246 from home:seife:testing 2009-10-12 06:19:56 +00:00
README.SUSE OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=38 2009-07-10 14:41:47 +00:00
ready OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/bluez?expand=0&rev=1 2008-09-15 08:31:24 +00:00

Notes about the SUSE bluez packages:
====================================

How does bluetoothd get started?
--------------------------------
Bluetoothd is started via udev. This means: as soon as a bluetooth device
is inserted, bluetoothd is started with the option "--udev".
For the case that D-Bus is not yet running during system bootup when the
adapter is detected, bluetoothd will quit with exit code 1, udev will notice
that and then try to restart bluetoothd later.

If you want to prevent starting of the bluetooth service, edit
/etc/sysconfig/bluetooth and set START_BLUETOOTHD to "no".

Have a lot of fun...