[Pkg-bluetooth-maintainers] Bug#492592: Bug#492592: bluez-utils: load bluetooth kernel module on before starting hcid

[Hendrik Sattler]

Am Sonntag, 27. Juli 2008 20:02:31 schrieb Filippo Giunchedi:
> > hcid (and probably other bluetooth stuff) will not startup if bluetooth
> > is only available as kernel module. Thus, not loading it makes those
> > pieces of software unusable. Thus, the init script should make a call to
> > "modprobe bluetooth" if e.g. /sys/class/bluetooth does not exist (or
> > whatever else is a clear indication that bluetooth is only available as
> > module and not built-in).
>
> Isn't it the duty of udev and/or module-init-tools (via /etc/modules) to
> load modules?

udev is only used if CONFIG_KMOD is enabled for the current kernel. In that 
case, starting hcid will load rfcomm, l2cap and bluetooth.

/etc/modules should just be used for cases that have no better solution.

An init script should at least try to meet the prerequisites for the program 
that it is about to start and in no case silently fail.

HS