| 1 |
Installation Instructions. |
| 2 |
------------------------- |
| 3 |
|
| 4 |
See below for installation on debian systems. |
| 5 |
|
| 6 |
This package requires docbook-to-man, libbluetooth, dbus plus make and a C compiler. |
| 7 |
|
| 8 |
To compile it use `make' |
| 9 |
|
| 10 |
To install it use `make install'. |
| 11 |
|
| 12 |
The default installation directories are /usr/share, /usr/sbin, |
| 13 |
/etc/bluemon. To install into /usr/local use `make PREFIX=/usr/local |
| 14 |
install'. Individual files can be relocated by setting the appropriate make |
| 15 |
variables: |
| 16 |
|
| 17 |
SBIN - binaries ($PREFIX/sbin) |
| 18 |
BIN - binaries ($PREFIX/bin) |
| 19 |
MAN - man pages ($PREFIX/share/man) |
| 20 |
DOC - documentation and examples ($PREFIX/share/doc/bluemon) |
| 21 |
CONFIG - config file (/etc/bluemon) |
| 22 |
|
| 23 |
It can be uninstalled with `make uninstall' with the same make variables set. |
| 24 |
|
| 25 |
Starting Bluemon |
| 26 |
---------------- |
| 27 |
|
| 28 |
The sample initscript should be copied to the system initscript directory and |
| 29 |
used to start the program. It uses a config file to read the parameters to pass |
| 30 |
to the program. The config file is searched for as /etc/default/bluemon, |
| 31 |
/etc/bluemon.conf or /etc/bluemon/bluemon.conf. If not, use man or --help to |
| 32 |
decide which parameters you wish to use. A good sample command line is: |
| 33 |
|
| 34 |
bluemon -qai 100 -t 210 -b BLUETOOTHADDR |
| 35 |
|
| 36 |
as root, and then as a user: |
| 37 |
|
| 38 |
bluemon-client -u "UP COMMAND" -d "DOWN COMMAND" -b BLUETOOTHADDR |
| 39 |
|
| 40 |
where UP COMMAND is executed when the signal passes the threshold upwards |
| 41 |
and DOWN COMMAND when it passes the threshold downwards. |
| 42 |
|
| 43 |
Debian |
| 44 |
------ |
| 45 |
|
| 46 |
This packages build-depends on docbook-to-man, libbluetooth1-dev, debhelper, |
| 47 |
devscripts, dbus-1-dev, fakeroot and build-essential. |
| 48 |
|
| 49 |
You will need to apply the debian diff first (should be distributed with the |
| 50 |
sources), then you can build a Debian package with either `make deb' or any |
| 51 |
of the normal methods of building a deb package (I suggest `debuild |
| 52 |
-rfakeroot -us -uc') |