BlueZ is Linux specific. To port this application to OpenBSD will potentially take significant time & understanding of OpenBSD's network stack (which is different than Linux). Because porting can be a very time-consuming activitiy, this site does not generally provide this level of support.

Recognize that both the libraries available on OpenBSD can be different than those available on Linux. OpenBSD's filesystem layout as described in hier(7) is also different. You should exhaustively check whether the existing applications already ported will take care of your needs before embarking on porting yourself.

I pointed you to sysutils/hcidump to suggest you look at the port framework, since it is a port of a bluez application. I do not know if the application itself would be of any value to you. As Ocicat eloquently stated, porting of Linux-specific applications requires knowledge of both Linux and OpenBSD software infrastructures. While looking the Makefile, I noticed the port does not have a $MAINTAINER, so questions about it (or other questions specific to bluez software porting efforts) are best taken to the ports@ mailing list.

I can't answer why your device now appears as a ugen(4) device rather than ubt(4) device without digging through driver source code, and related CVS logs, which I do not have the time to do today. And, even if I did have the time, I might not be able to find the change that affects your specific device.

Me neither, I don't own any bluetooth gear.. and quite frankly I don't see much need for support on OpenBSD, it's really not that more difficult to bring the USB data cable or use 802.11 wireless instead.

Me neither, I don't own any bluetooth gear.. and quite frankly I don't see much need for support on OpenBSD, it's really not that more difficult to bring the USB data cable or use 802.11 wireless instead.