## Metadata

%product Foo
%copyright 2000-2007 by Foowhizzer.
%vendor Foocom
%license COPYING
%readme README
%description Foo server.
%version 2.2.2 1

## Filelist

$prefix=/usr/local

f 755 root sys ${prefix}/bin/foo foo
i 755 root sys fooinit fooinit

## Scripts

%preinstall << EOF
echo “doing pre install, enter your name:”
read name
echo “oh hai, $$name, thx for installing”
EOF

%postinstall << END_OF_POSTINSTALL
echo “doing postinstall”
END_OF_POSTINSTALL

And thats it. Run epm and get a deb, rpm, tgz, pkg or whatever.

Given that these two utilities are from the same project, you think they would play nice.

The second is this excellent overview of ICT for development from Patricia Daniel, which makes clear that OLPC/XO-1/the $100 dollar laptop will not be operating in a vacuum in the developing world. David, our deputy editor, has been trying to source a piece like this for a long time – it’s a really useful summary of schemes in the Global South. What I took from it is, much ilke Web 2.0 hype in the West, the projects that work are the ones that are user-orientated, and that people want to use.

Turns out, nokia have changed the bluetooth channel from 1 to 2, as sdptool reveals:

~$ sdptool browse xx:xx:xx:xx

…..

Service Name: Dial-Up Networking
Service RecHandle: 0×10008
Service Class ID List:
“Dialup Networking” (0×1103)
Protocol Descriptor List:
“L2CAP” (0×0100)
“RFCOMM” (0×0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0×454e
encoding: 0×6a
base_offset: 0×100
Profile Descriptor List:
“Dialup Networking” (0×1103)
Version: 0×0100

So, if you want to get it working, just change your /etc/bluetooth/rfcomm.conf to a new channel:

rfcomm2 {
bind yes;
# Bluetooth address of the device
device xx:xx:xx:xx;
# RFCOMM channel for the connection
channel 2;
# Description of the connection
comment “Example Bluetooth device”;
}
PS, you can get chat scripts here

First off, the build quality seems pretty poor. Its one of those slidey phones and the top part feels slightly loose. It wobbles from side to side in your hand – not what you expect from a new piece of kit. Secondly, orange seem to have done all they can to screw the UI. For example, straight after you take a snap it pops up a dialog box with two options: ’save to gallery’ or ’send to friend’. What’s the thing these two have in common? They both make money for Orange. The option ‘just save it to the 128meg SD card’ is completely absent. You have to press cancel, which is pretty hidden and unintuative, to get this behaviour.

The ‘gallery’ which that dialog box is speaking about is a web based piece of software from pixota which it seems orange *really* want me to use. Hence the other genius idea that orange had: to put this gallery as the first option on the phones ‘home page’ instead of contacts. This is where the cursor starts when you unlock your phone, and every time you press it by mistake the phone attempts to make a 3g connection, and so on, resulting in a pissed off phone user. I haven’t found out a way to change this, but given the labyrinthine nature of the series 60 menus, this could be my fault.

Now all that remains is getting this baby to work with ubuntu. Contact syncing I didn’t have much hope for given my previous experiences with opensync. The opensync version packaged with dapper is hopeless, but I did find subversion packages which gave me some hope. I did get the phone syncing this way with msynctool, and msynctool reports that it is sending stuff to the phone. The phone, however, steadfastedly refuses to show any of these changes.
So if syncing won’t work, what about getting the photos off the phone. The N80 has a mode where it can act as a USB storage device, so that should be simple right? Well, not exactly. It requires a kernel patch and I really don’t feel I have time for a kernel patch these days. That’s why I’m using ubuntu, right?
In the end, I have a nice brand new phone with no way of getting the pictures off and no way of doing a decent sync (google calendar, anyone?).