1INSTALLING BottleRocket:
2-----------------------
3
4./configure
5make
6make install
7
8Note: The Makefile assumes that your make program
9is GNU gmake; if this is not the case, you will need
10to hand-edit the Makefile for your platform after
11running configure.  If you need help, email me
12(my email address is in the README file).
13
14That's it!  Note that BottleRocket requires access to
15the serial port that your FireCracker is plugged into,
16so you need to be root to use it, or set it up setgid
17(generally group tty) for other users to use it (this
18is definitely recommended over making it setuid).
19It's always a good idea to look over code that you're
20going to be running with elevated privileges (do that
21now!) to make sure you're comfortable with it having
22higher privileges.  Also be aware that just making it
23setgid (or uid), executable by anyone, means that
24*anyone* on your system can use it to turn thing on/
25off, and IT IS POSSIBLE TO CAUSE A MODEM PLUGGED IN
26THROUGH THE DYNAMITE MODULE TO LOSE CARRIER.  If the
27process is killed at the right time, DTR and/or RTS
28will be set low and can remain that way.  There is
29no way to stop a user from sending a SIGKILL to a
30process that they have run, even if it's setuid/gid, on
31at least most operating systems that I'm familiar
32with.  YOU HAVE BEEN WARNED.
33
34You can now specify the serial port (or a link to a
35serial port) from configure; use
36
37./configure --with-x10port=<device>
38
39(I recommend using --with-x10port=/dev/firecracker, and
40then linking /dev/firecracker to the device you want to
41use; this makes it easier to fix things if you move the
42firecracker to another port)
43
44to do this.  Use
45
46./configure --help
47
48to get a full list of options you can pass to configure.
49