84393 – /etc/init.d/bluetooth script depends on hotplug instead of coldplug

Bug 84393 - /etc/init.d/bluetooth script depends on hotplug instead of coldplug

Summary: /etc/init.d/bluetooth script depends on hotplug instead of coldplug

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal
Assignee:	Mobile Herd (OBSOLETE)

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:

Reported:	2005-03-07 06:32 UTC by Laurent Gottely
Modified:	2005-04-28 01:14 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Laurent Gottely 2005-03-07 06:32:41 UTC

/etc/init.d/bluetooth script depends on hotplug instead of coldplug. At boot, the bluetooth service is started first and sdpd failed because RFCOMM socket domain not implemented

Reproducible: Always
Steps to Reproduce:
1.rc-update add bluetooth default
2.rc-update add coldplug default
3.reboot

Comment 1 Henrik Brix Andersen 2005-03-22 11:02:06 UTC

I'm not sure I understand the problem?

Comment 2 Laurent Gottely 2005-03-23 10:42:12 UTC

The BT hardware need to be detected before you can use it. As coldplug replace 
hotplug to detect hardware at startup, the bluetooth script should depend on 
it. I change it and it work perfectly for me, but perhaps the canonical way 
is to put  coldplug at boot level and not default. But then why the 
dependance on hotplug ?

Comment 3 Henrik Brix Andersen 2005-04-28 01:14:42 UTC

This is fixed InCVS.