Quick Start
|
175
3. The bluez-utils and bluez-sdp packages configured themselves to start in
runlevel 3 and 5. After installing these packages, we started them with
the following commands (but we could also have rebooted):
/etc/init.d/bluez-utils start
/etc/init.d/bluez-sdp start
4. The /dev/rfcomm* devices already exist, so we didn’t need to create
them.
SuSE 9.0
We used SuSE 9.0 (FTP install) with the latest available kernel package
(2.4.21-166-default). To enable Bluetooth, we followed these steps:
1. Installed the following packages using YaST:
• bluez-bluefw
• bluez-libs
• bluez-pan
• bluez-sdp
• bluez-utils
2. The packages configured themselves to start in runlevels 3 and 5. After
installing these packages, we started them with
/etc/init.d/bluetooth
start
(but we could also have rebooted).
3. The /dev/rfcomm* devicesdid not exist, so we created them as shown in
Example 7-4.
Mandrake 9.2 and RedHat 9
On Mandrake, we used the latest available kernel package (2.4.22-10mdk),
but on Red Hat, we rebuilt the kernel the same way we built it for Debian.
For rfcomm to work on RedHat and Mandrake, we followed these steps:
1. Downloaded the following RedHat RPMs from http://bluez.sourceforge.net:
• bluez-bluefw
• bluez-hcidump
• bluez-libs
• bluez-pan
• bluez-sdp
• bluez-utils
2. Next, we ran
rpm --test -ivh bluez-*, and all looked well, so we
installed them with
rpm -ivh bluez-*.
Komentáře k této Příručce