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

How does bluetoothd get started?
--------------------------------
Bluetoothd is started via D-Bus activation. This means: as soon as somebody
is requesting bluez services via D-Bus, bluetoothd is started.
Additionally, there is a udev rule that runs /lib/udev/bluetooth.sh every
time a bluetooth device is plugged into the system. This script sends a
request via dbus-send to start the bluetoothd.
For the case that D-Bus is not yet running during system bootup when the
adapter is detected, the script creates /dev/shm/bluetooth-adapter-present/
which is used in a later init script /etc/init.d/bluetooth-coldplug to
decide if bluetooth services should be started or not.

Of course you can still decide to always start bluetoothd on every boot by
issuing the "insserv bluetooth" command or enabling it with the YaST2 runlevel
editor.

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

Have a lot of fun...