Convert SVN repository to a GIT repository

Steps I followed to convert my SVN repository to a GIT repository.


svn log -q | awk -F '|' '/^r/ {sub("^ ", "", $2); sub(" $", "", $2); print $2" = "$2" <"$2">"}' | sort -u > authors-transform.txt

then I editted the authors-transform.txt to have my name fully spelled out and my e-mail address filled in.


git svn clone [SVN repo URL] --no-metadata -A authors-transform.txt --stdlayout ~/temp --prefix=origin/

the important part for me was adding the –prefix=origin/. Without this, it all becomes a big mess because?the remote branches will have an empty prefix which makes things harder for you in the future.


To create a .gitignore file based on your svn:ignore properties use the following command:

cd ~/temp
git svn show-ignore -i origin/trunk > .gitignore
git add .gitignore
git commit -m 'Add .gitignore from svn:ignore properties'

Again the critical part for my situation was to add the -i origin/trunk (or –id). Without it it doesn’t know what SVN branch you want the properties off.

All of this was shamelessly copied from with some modifications to really make it work, because that post is a little outdated. Credits to John Albin.


modesetting instead of xf86-video-intel plus benchmark

Today I stumbled upon this reddit-article.

It speaks about using the modesetting driver shipped with xorg instead of the xf86-video-intel driver. I did a benchmark with the xf86-video-intel and the modesetting driver to see which performs better in order to decide if I will drop xf86-video-intel. Here are the results:

Unigine-valley Basic preset @xf86-video-intel:

FPS: 14.4
Score: 604
Min FPS: 8.2
Max FPS: 33.1

Unigine-valley Basic preset @modesetting:

FPS: 23.5
Score: 984
Min FPS: 11.8
Max FPS: 40.3

It doesn’t really matter what hardware I’m using, all that matters is that the situation improved. But for reference: Intel HD Graphics 5500.

So my choice is simple, I’m ditching xf86-video-intel in favor of using modesetting, which was already installed on my system together with xorg-server.

backlight issue

because of the switch to modesetting driver the xbacklight utility does no longer work. Using a xorg config file with the Backlight option set to intel_backlight also does not work as a workaround. So I installed light-git (from the AUR) which allows me to control my laptop backlight once again.

Maak een Ubuntu 16.04 live usb-stick met Rufus

Ubuntu 16.04 LTS is op 21 april 2016 uitgekomen. LTS staat voor Long Time Support en daarom is dit een versie van Ubuntu die het waard is om de komende tijd te gebruiken door middel van een live usb-stick.

Met Rufus een Ubuntu 16.04 LTS live usb-stick maken

Dit artikel legt je uit hoe je met behulp van Rufus een Ubuntu 16.04 live usb stick maakt. Volg de stappen:

  1. Ga naar
  2. Klik op Download (rechtsboven, links naast zoekveld)
  3. Klik op “Ubuntu Desktop >”, je komt nu op een pagina waar staat Ubuntu 16.04 LTS
  4. Klik dan op de oranje Download knop
  5. Nu willen ze dat je gaat doneren, scroll helemaal naar beneden en klik op “Not now, take me to the download”
  6. De download start in paar seconden
  7. Ga naar
  8. Scrol een beetje tot je Download ziet en kies dan voor Rufus 2.8 Portable
  9. Start rufus. Er wordt gevraagd of je online wilt zoeken naar programma updates. Klik maar op nee. Het programma start verder op. Doe je usb stick van 4GB of groter in je computer… even wachten tot je computer de usb stick herkent.  Kies je Apparaat (usb stick) in de eerste dropdown, vul de rest in zoals de afbeelding weergeeft. Het veld Clustergrootte wordt automatisch ingevuld. Klik op het icoontje met een cd+drive om te browsen naar de ubuntu-16.04-desktop-amd64.iso. Het veld Nieuwe volumelabel wordt nu automatisch ingevuld.
  10. Druk nu op Start.
    afbeelding van Rufus waarmee een Ubuntu 16.04 LTS live usb stick gemaakt wordt
    Rufus instellingen om een bootable Ubuntu 16.04 LTS live usb stick te maken

    (Het kan zijn dat er gevraagd wordt om een paar bestanden te downloaden die met syslinux te maken hebben, klik dan op Ja, zodat rufus deze automatisch voor je download.)
    Er wordt nog een laatste keer gevraagd of je echt wilt doorgaan, klik op OK als je zeker weet dat je het juiste apparaat hebt geselecteerd.


Start nu je computer opnieuw op en start op vanaf de usb stick die je net hebt gemaakt door in je bios de boot order zo in te stellen dat je USB device bovenaan staat. Sommige computers geven ook een boot optie aan om tijdens het booten eenmalig de opstart disk te kiezen, dit is handiger dan de vorige optie omdat je nu geen bios instellingen permanent hoeft te veranderen.

partclone restore exit error

Over the last three years I have made a lot of disk clones with clonezilla. I did this before reinstalling another OS or just to backup, but I always did it quickly. That means I just cloned the disk and never looked at it again. I only had to restore two or three times.

The problem is that because I did not really document anything about what is in the image, I now have no clue if I still want to keep image X or image Y. I need to see what is in the images…

So I’m restoring  images by cat’ing together the compressed pieces of my images and decompressing them and piping that stream into partclone restore utility.

Now I keep getting this very obscure error:
Partclone v0.2.80
Starting to restore image (2013uncompressed.img) to device (2013.iso)
UID is root.
source=2013uncompressed.img, target=2013.iso
open source file/device 2013uncompressed.img
open target file/device 2013.iso
device (2013.iso) is mounted at
error exit

I have no clue what to do with that. So I downloaded an old version of clonezilla that contained the same version of partclone that the cloned image was made with. That gave the same error. Then I found an answer on askubuntu with zero rating. Just create the file first before you issued the partclone.restore. So to summarize:

touch /dir-to-new-image/partition.img
sudo cat /dir-to-images/partitionname.gz.* | sudo gzip -d -c | sudo partclone.restore -C -s - -O /dir-to-new-image/partition.img

So in the end this was super easy and I did not even need a clonezilla live usb. I could just do this from arch linux using partclone 2.80.

Thanks to:

Server refused our key

I have been trying all day to set up SSH keys on a linux server and Windows 7 client, finally with succes.

The way I managed to finally do it is like this:

  1. Log into your linux server
  2. Type:
    ssh-keygen -t dsa
  3. Accept default filename
  4. Provide a strong passphrase
  5. The keygen will create two files:, and id_dsa. The first one is the public key (.pub), the second one it the private key, copy this to your Windows 7 client.
  6. While stil on your server, now put the contents of into ~/.ssh/authorized_keys
  7. Make sure you
    chmod 600 ~/.ssh/authorized_keys
  8. Now move to your Windows 7 client and run puttygen.exe
  9. Load the id_dsa you have copied from the server
  10. Enter the passphrase
  11. Now use the save private key button to save the private key in putty .pkk format
  12. Now open putty and go to: Connection » SSH » Auth and browse for the .pkk to use as private key
  13. Now click open and you should be able to login into your server without the text: Server refused our key

If you followed the above and it still shows the text: Server refused our key, just read on…

Bonus steps that might solve your problem:

  1. In your server console issue the command: hostname
  2. Your hostname will be shown now, write it down or remember it
  3. Now start putty and in the Host Name (or IP address) input field enter that hostname (I am assuming you have allready set up a working hostname)
  4. With the .ppk selected as in step 11 press Open and you will be able to login without the text: Server refused our key

The first 13 steps are quite obvious, but it took me some time to notice that you really have to use the hostname. Before when I was just using a local IP address like I could still login with putty, but the key would not be accepted, now that I’m using my hostname I can succesfully login on the server. There are a lot of tutorials like this one on the web, but none of them told me to use the hostname you have set up on your server!