Just while we’re on the subject of Linux. I’ve just installed Fedora Core 6 on my laptop, and been blown away by the progress that it has made in the past couple of years. It’s almost user friendly! The much talked about Compiz (or in my case Beryl) is simply stunning, whilst improvements in the general look and feel of Gnome and KDE make it much more user friendly. There have been problems before with hardware compatibility, but from the box (or DVD), sound, touchpad, VGA, LAN, and bluetooth were working nicely. Wireless took a little tweak to have working shortly afterwards (Firmware for the ipw2100 was required). I shall check later this evening to see if video works ok, but given that I’ve already made my way through an excellent FAQ, I’m sure it already will be.

I guess all Linux needs now is Office and Photoshop! (Yes, I know about wine and crossover).

• Firstly, the plugin will not let any user post who has turned off JavaScript. JavaScript is essential for the calculation of the “hashcash_value”
• And secondly, the plugin may have issues when the end user is behind a proxy server. I personally am behind a proxy server at work and have tested this, finding it to work every time I checked it. It is however a theoretical problem.

This plugin makes the Askimet plugin seem pointless. In fact, I’d probably recommend getting this, and turning off the Askimet plugin. I wouldn’t get rid of it though, it’ll no doubt be needed if spammers include JavaScript engines in their spambots.

The main reason for this post is that there is a small bug in the code which prevents it from working with Wordpress 2.1 . Here is the fix:
function TestWPVersion() {
if (substr(get_bloginfo('version'),0,1) == 2) {
return true;
}
return false;
}

If anyone is interested in how to get Postie to work with an mbox file, just add a message below.

Firstly ensure that Bluetooth is installed on your computer, and that it is working. I’m using Fedora Core 5 (FC5), so to do this is as simple as (assuming you have yum set up properly:
# yum install bluez-*
We don’t really need all of the packages here to do this, but you will no doubt find those that are installed useful.

Insert your dongle here (assuming you’re using a USB Bluetooth device, if Bluetooth is built in, ignore this next bit). You may, depending on how your computer is set up, have to reboot here – I have no idea how to detect added hardware! I’m sure there is a better solution to this, but unfortunately I don’t know what it is. Now test the Bluetooth, which should give you output similar to below.
$ hcitool dev
Devices:
hci0 11:22:33:44:55:66
Assuming you’ve got this far and everything is working, you can now try the more interesting bits. I’m going to assume that you’re wanting to connect a phone to your computer, and monitor the presence of the phone. If you’re intending on using something else (TomTom, GPS box, PDA, whatever), then just use that whenever I mention phone – simple. Turn on Bluetooth on the phone, and scan for the device from the computer
$ hcitool scan
Scanning ...
00:AA:BB:CC:DD:EE phone
This will give you the name, and the id of your phone (and also any other devices in range). Make a note of the ID/Mac address (the letters/numbers/colons bit), we’ll need this later. Now, what we’re going to use to detect the presence of your phone is this Mac address. If you scan specifically for the Mac address when the phone is in range, then the hcitool program returns the name of the phone, if the phone is out of range, then NULL is returned:
$ hcitool name 00:AA:BB:CC:DD:EE
phone
The results from this are best piped into a file, which can then be used to monitor the presence of your phone. A simple bash
script to do this might look like this:
#!/bin/bash
## usage:
## detectphone time mac output_file_name
## Where:
## time - Is the time in minutes between detection attempts
## mac - Is the mac address of the device to attempt to detect
## output_file_name is the filename to write the output to!
if [ ! -n "$3" ]
then
echo "usage: detectphone time mac outputfile &"
exit 2
fi
## Simply put the program into a loop, sleeping for the first argument each loop
## and looking for the device with the id equal to the second argument each loop.
## The output from this is saved to the third argument
while [ "$var1" != "end" ]
do
`hcitool name $2 > $3`
`sleep $1`
done
Next we need a script which will check for the content of the file produced above and for it to then produce an action. Note, we don’t put the above check in to the script, as it would mean that for each action you want to do, you would have to check for the presence of the phone, whereas doing the above, the phone is only checked for once, no matter how many scripts you have. The following scripts can be executed periodically, or could have a loop in like the above script.
#!/bin/bash
## This script should be reproduced as the top of all the scripts that you create.
## Usage:
## fileexists pathtodetectionfile
if [ ! -n "$1" ] # Ensure that the path to the file was passed
then
echo "usage: fileexists pathtodetectionfile"
exit 2
fi
if [ ! -e "$1" ] # Check if file exists.
then
echo "$1 does not exist.";
exit 2
fi
output=`ls -l "$1" | awk '{print $5}'`
if [ $output == 0 ]
then
# File length is 0, exit quietly
exit 0;
fi
## If the script reaches this point, then everything has worked, and the phone
## has been detected.
## Insert your application logic HERE ##
## Insert your application logic HERE ##
exit 0;
If you’d prefer a script that executes a particular function when the phone comes into range, or moves out of range, then the following will probably be useful.

I know this is a little open ended, and that I’m not really finished with this, but I felt the need to post this as it has been sitting on my computer for far too long.

It appears I am not the only person who feels that OpenLDAP (or Fedora Directory Server) is a little too much for a simple contacts server. Is there not a better solution out there somewhere?