Hi, now with the fancy udev autostart, we have everything in place to get rid of the init script. However, it does not work. See e.g. https://bugzilla.novell.com/show_bug.cgi?id=527856 Kay told me that in his opinion, udev is doing everything correctly and that using it to fix boot dependencies is not an option. So I'm going to pack up a simple bluetooth init script that does nothing but udevadm trigger --subsystem-match=bluetooth And, as Kay has found out, fedora does the same: http://cvs.fedora.redhat.com/viewvc/devel/bluez/bluetooth.init?view=markup&sortby=date So the question is: how should we handle this upstream? Or should every distribution roll her own solution? Best regards, Stefan -- Stefan Seyfried R&D Preload Department | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." This footer brought to you by insane German lawmakers: SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
