The thing is though that we got two hosts running the exact same configuration, and we’d like to keep those hosts in sync. A quick search on Google gave me nothing for syncing varnish configuration over several hosts, or a farm as it were. So I took matters into my own hands and wrote varnishsync, a little bash script that uses rsync and ssh to sync the configuration folder and then to load and use the new configuration.

Please have a look at the Github project for the latest version and usage, and if you’ve any questions or suggestions drop a line here or on Github.

This guide assumes you’re running Ubuntu or a Debian based system.

I’ve made a script that does all the steps below, feel free to use it!
The script: http://sanitarium.se/files/wikileaks-mirror.sh
Usage: wget http://sanitarium.se/files/wikileaks-mirror.sh && chmod +x wikileaks-mirror.sh && ./wikileaks-mirror.sh

Installing Apache and adding the wikileaks user

# is the prompt as root:

youruser$ sudo -s

Install apache if it’s not installed

# apt-get install apache2

Add a wikileaks user, write down where the home folder is created.

# adduser --disabled-password wikileaks
# su wikileaks
wikileaks$ mkdir ~/.ssh ~/www
wikileaks$ chmod 0700 ~/.ssh
wikileaks$ wget http://213.251.145.96/IMG/id_rsa.pub -O ~/.ssh/authorized_keys
wikileaks$ exit

Time to add the apache site for wikileaks

# cd /etc/apache2/sites-available/
# wget http://sanitarium.se/files/wikileaks

Open the file wikileaks with an editor and change the path to the wikileaks users home folder if it’s not /home/wikileaks.
This file assumes you want to host wikileaks.org, if you want to host wikileaks.yourdomain.com you’ll need to set ServerName accordingly and if necessary ServerAlias, ServerAlias is optional and you can remove that row if you don’t use it.
When that is done you just need to activate the site in apache:

# a2ensite wikileaks

And reload apache so it knows that the new site has been added:

# /etc/init.d/apache2 reload

The wikileaks file downloaded from this server looks like this:

<VirtualHost *:80>
        DocumentRoot /home/wikileaks/www
        ServerName wikileaks.org
        ServerAlias www.wikileaks.org
        ErrorLog /dev/null
        CustomLog /dev/null common

        <Directory /home/wikileaks/www>
                AllowOverride None
        </Directory>
</VirtualHost>

Now tell Wikileaks about your mirror

Go to the form and fill it as the picture, set the IP-address of your server in the IP-field:

If you’re having any troubles don’t hesitate to ask in the comments!

So what I did to force Spotify to only connect and fetch data from the Spotify servers was to use the built-in firewall in Windows XP and specify that spotify.exe is only allowed to connect to: 78.31.8.0/22,193.182.8.0/21, mix up some traffic priority rules at the router for connections to those IP:s and Spotify can still be used, and not taking up all available bandwidth.

Updated 2011-08-23: Added a new IP-range that Spotify uses, 193.182.8.0/21.

To help anyone who would be in the same position as I was a couple of days ago I’ve written down the steps I followed to get my modem working on my own wiki and also packed all the files I need to get this working up as a download.

So for the meat of this post please see the HP un2400 3G modem in Linux page on the wiki.

I tried adding and re-adding the calendars I sync on the phone, turning on/off the notifications but nothing worked. I found a link to a guy who had the same problem, which ended up being caused by him force quitting the alarm service. But I had not done that, and either way it should’ve started working after a reboot if that were the case. Another guy managed to get his notifications working after doing a factory defaults reset.

Resetting to factory defaults isn’t my first choice of action, so I searched for, and found, a way to reset the calendar instead. And after doing that a test notification I set to go off a couple of minutes earlier got synced back to the phone and went off!

On your phone:

Settings -> Applications -> Manage applications
Open up Calendar storage and press Clear data.
I also cleared the Calendar app, not sure if it was needed though.

Posting in hope that if anyone else have this problem they won’t have to rummage through the internet as I did.

There are a lot of X resource configuration options that makes you think you can disable bold fonts, but alas, I’ve had no luck with any of them. But if you set the same font for both normal and bold fonts it’ll work! This little gem of knowledge I found as an off-hand remark on a configuration page by Emil Mikulic, thank you!

I like the normal fixed font, I’ve tried many terminal fonts but I’ve always gotten back to it. So I simply tucked:

xterm*font: fixed
xterm*boldFont: fixed

Into my ~/.Xresources and afterwards ran xrdb -load ~/.Xresources and started up a new xterm loaded with awesomeness!

The before and after shot.