Things you need, and the versions I used (in order of building):
In addition, my YDL machine needed ImageMagick >= 5.4.7 and ucd-snmp-devel (and ucd-snmp probably, maybe ucd-snmp-utils if you feel like it). I also used the latest version of the airo_cs driver. Install these packages before building the above.
I grabbed the ucd-snmp SRPM from Red Hat 7.3 and rebuilt it in YDL
2.3. Ethereal (IIRC) uses the ucd-snmp-devel package; while it’s not
required, I tried to build as much stuff in as I could. You will need
to edit your /usr/include/ucd-snmp/snmp.h file, though, for
Ethereal’s configure script to successfully enable its SNMP support.
After:
#ifdef __cplusplus
extern "C" {
#endif
Which is near the top, add:
#include <ucd-snmp/asn1.h>
Also, the ImageMagick SRPM from RH 8.0 seems to be broken WRT include files. Here’s my ImageMagick spec file that worked for YDL 2.3.
ucd-snmp and ImageMagick I built RPMs for and installed. The other
stuff I kept in my (non-root) user’s home directory. I made a root
directory there. Use this root directory with the --prefix option
for all the packages’ configure scripts. Building with PPC I also
put RPM’s value for RPM_OPT_FLAGS in the CFLAGS environment
variable before I ran the configure scripts. For example, I built
Kismet with:
CFLAGS='-O2 -fsigned-char' ./configure --prefix=$HOME/wireless/root
--with-ethereal=$HOME/wireless/ethereal-0.9.7
--disable-setuid
(BTW, IIRC you can see rpm’s value for RPM_OPT_FLAGS with rpm
--eval '%{optflags}n'.) After doing this don’t forget to edit the
path to any files in kismet.conf and kismet_ui.conf. Also,
beware that there may be a bug in either the newest airo_cs driver or
in YDL’s 2.4.19-4a kernel. If you have problems finding files in
/proc/driver/aironet reboot the system.
I edited the kismet script as well, to make it run without
assuming it’s suid root (and without assuming . is in the path).
Here’s my kismet
script.
Battery life on darkbook seems good enough. Probably something like
three hours. I thought I could use pmud to put the system into
“low power usage” or something like that, but if so I can’t figure out
how to do that now. Actually, while I was typing this the system
suddenly went from 0:22 minutes showing in the battery meter on my
Gnome panel, to warnings on my screen saying “one minute remaining”,
to going into snooze. At least it figured out that (perhaps?) the
battery remaining time was wrong and put the system to sleep.