Unusual Git usage : temporary commit into a local SVN checkout

I really love Git, the distributed source code management designed by Linus Torvald. It is VERY easy to setup a new local repository (just type git init in the root of your working directory). I do it all the time, even for a simple bash script creation. Even for the simple text files I use as TODO lists.

A few days ago, I add to work offline in an old SVN checkout. I wish I could have used git-svn but it was an old checkout, and I was offline now. So much for git-svn for now...

I had to find something to be able to undo my changes while I was offline. So why not try Git in a local SVN checkout ? After all, the only thing that Git does is to create a .git file, it does not modify the local files if I don't want to.

So, at the root of my SVN checkout directory :
git init
Then, I must hide the .svn metadata directory, so I modify .git/info/exclude and I add the line :
.svn

Now Git will ignore the .svn directories and I can type :
git add .
git commit

Now at least I can regularly commit my changes into Git and go back in time if
I badly break my unit tests during my TDD session. Of course when I'll be back online
and I'll commit into the SVN repository I'll lose the commit history in Git, but as I
was offline anyway, at least I could work with a safety net.

Even used in this unusual way, Git is still useful.

JAgraffe : quickly send your pictures by email

I had coded JAgraffe two years ago for my own use. I still use it almost on a weekly basis.

Usual GnuPG commands

I tend to forget these very usual GnGPG commands as I use them only once in while. Now I won't forget them, or at least I'll known how to quickly find them :

Sign a file :
<br />gpg --detach-sign --armor myfile.tar.gz<br />
Encrypt and decrypt a file for my own use :
<br />gpg --encrypt --recipient 'MyName' foo.txt<br />gpg --output foo.txt --decrypt foo.txt.gpg<br />
Encrypt a free text for someone :
<br />echo 'Hello world' | gpg --output encrypted_hello.txt --encrypt --armor -r myfriend@whatever.com<br />
Get my own fingerprint :
<br />gpg --fingerprint myaddress@whatever.com<br />

Mix RJ45 and coaxial (10Base-2) ethernet cables

Problem : how do you add a WIFI AP (Access Point) to an already existing network wired with 10Base-2 coaxial ethernet cables ?

Of course this is an old network with old PC, and you can not replace the 10Base-2 network adapters of the PC in order to rewire with RJ45 cables.

Answer : just find one more 10Base-2 network adapter in a drawer, and add it in an old Linux box that already has a RJ45 network adapter.

Setup two subnetworks, one on each adapter of the Linux box, with routing of the traffic from one subnetwork, to another (or even better, build a bridge, in order to have one single subnetwork).

Plug in the AP to the linux box with a crossover RJ45 ethernet cable.

This linux box can even be used as a gateway both for the LAN and for the WLAN !

Simple iptable gateway script

It's the second time I must setup a Linux gateway connected to a DSL line. The DSL modem interface is ppp0 and the LAN interface is eth0. Here is the script I use to setup the iptables :

<br />echo "1" > /proc/sys/net/ipv4/ip_forward<br /><br />modprobe ip_conntrack_ftp<br /><br />export EXT=ppp0<br /><br />/sbin/iptables -F<br />/sbin/iptables -t nat -F<br />/sbin/iptables -t mangle -F <br />/sbin/iptables -X <br /><br />/sbin/iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT<br />/sbin/iptables -A INPUT -m state --state NEW -i ! $EXT -j ACCEPT<br />/sbin/iptables -P INPUT DROP<br /><br />/sbin/iptables -A FORWARD -i $EXT -o eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT<br />/sbin/iptables -A FORWARD -i eth0 -o $EXT -j ACCEPT<br /><br />/sbin/iptables -t nat -A POSTROUTING -o $EXT -j MASQUERADE<br /><br />/sbin/iptables -A FORWARD -i $EXT -o $EXT -j REJECT<br />

Sort JPG images by EXIF date in Ruby

Everybody now has a digital camera, and, during special events everybody takes plenty of pictures, and you end up with all these JPG images from different cameras. Each set of pictures tells the same story from the beginning, so it would be great to be able to reinterleave all of them in order to tell one single story.

That what the folllowing little Ruby script does, thanks to the libexif-ruby library. If you run it in a directory with JPG images, it will create a subdirectory and copy all images, renaming them, prefixing with the EXIF date set by the camera.

First, install the libexif-ruby library. On Ubuntu you can type :
<br />sudo apt-get install libexif-ruby<br />
Then copy the following script in a ruby script file :
<br />#!/usr/bin/ruby<br /><br />require 'exif'<br />require 'ostruct'<br />require 'fileutils'<br />include FileUtils::Verbose<br /><br />SUBDIR='exifsorted'<br /><br />files = Dir.glob('*.{JPG,jpg}').entries.map { |name| OpenStruct.new({"name"=>name, "date"=>Exif.new(name)['Date and Time'].gsub(/ |:/,'')})}<br />if(File.exist?(SUBDIR))<br /> puts("Error : #{SUBDIR} directory already exist, delete it")<br /> exit(1)<br />end<br />mkdir SUBDIR<br />files.each do |file|<br /> cp(file.name,File.join(SUBDIR,file.date + '_' + file.name))<br />end <br />

Linux and Logitech MX mouses resolution

Without its real driver, my Logitech MX 510 mouse is seen by Linux as a 400 cpi resolution mouse. Actually it can be used in 800 cpi thanks to lmctl

I've added this script to the 'Startup Program' list of Gnome :
<br />#!/bin/sh<br />lmctl -8<br />xmodmap -e "pointer = 1 2 3 4 5 8 9 6 7"<br />
The xmodmap call allows to properly configure the thumb buttons.

An other Nautilus script : create directory with date

I've already described how to add custom scripts for Gnome file manager, Nautilus. So here is a an other simple script : it allows to create a directory with the name prefixed by the current date, via the contextual menu (right click) of Nautilus in the window of an other directory.
Just type the name of the directory in the popup dialogue ; spaces will automatically replaced by underscores.

You must install XDialog to be able to use this script.
On Ubuntu :
<br />sudo apt-get install xdialog<br />
And here is the script :
<br />#!/bin/sh<br /><br />CURRENTDATE=`date +%y.%m.%d`<br />DIRNAME=`Xdialog --title "Directory with date creation" --inputbox "Date : $CURRENTDATE\nDirectory name ?" 8 45 2>&1`<br />case $? in<br />0) mkdir $CURRENTDATE.${DIRNAME// /_};;<br />1) exit;;<br />esac<br /><br />

Nautilus File Manager scripts : Scale JPG images

I really appreciate the feature of Nautilus (Gnome file manager) that allows the use of custom scripts via the right click contextual menu. To be seen by Nautilus, the scripts must be copied in a specific directory ; you can reach this directory with :
Right clic in any directory window --> Scripts --> Open Scripts Folder

For example here is a bash script that can be used to scale all JPG images in a directory (a directory is created and the scaled images are copied into this directory).

You must install XDialog and ImageMagick to be able to use this script.
On Ubuntu :
<br />sudo apt-get install xdialog<br />sudo apt-get install imagemagick<br />

Then copy the script in the script directory of nautilus :

<br />#!/bin/sh<br /><br />CURRENTDIR=`pwd`<br /><br />SIZE=`Xdialog --stdout --title "Image Scaling" --radiolist "Scaling images in \n$CURRENTDIR\npick a size !" 0 0 0 640 "640 pixels" 0 800 "800 pixels" 0 1024 "1024 pixels" 0 1920 "1920 pixels" 0 2>&1`<br /><br />if [ "$?" = "1" ] ; then<br /> exit 0<br />fi<br /><br />TARGET="R"$SIZE<br />mkdir $TARGET<br /><br />for j in '*.jpg' '*.JPG' ;do<br /> for f in $j ;do<br /> convert -quality 88 -geometry $SIZE "$f" $TARGET/"${TARGET}_$f"<br /> done<br />done<br /><br />Xdialog --title "Image Scaling" --msgbox "Image scaling done in :\n"$CURRENTDIR/$TARGET 0 0<br /><br />exit 0<br />

Simple CruiseControl + Ant example

I always have a hard time finding online a simple example of CruiseControl + Ant file whenever I need to quickly setup a Continuous Integration server for a project. So here is the configuration I had set up for the open source project TSP (Transport Sample Protocol) :

<br /><cruisecontrol><br /> <project name="tsp" buildafterfailed="false"><br /><br /> <listeners><br /> <currentbuildstatuslistener file="logs/${project.name}/status.txt"><br /> </listeners><br /><br /> <bootstrappers><br /> <cvsbootstrapper localworkingcopy="projects/${project.name}/make" file="cc-build.xml"><br /> </bootstrappers><br /><br /> <modificationset quietperiod="30"><br /> <cvs localworkingcopy="projects/${project.name}"><br /> </modificationset><br /><br /> <schedule interval="300"><br /> <ant anthome="apache-ant-1.6.5" buildfile="projects/${project.name}/make/cc-build.xml"><br /> </schedule><br /><br /> <log><br /> <merge dir="projects/${project.name}/target/test-results"><br /> </log><br /><br /> <publishers><br /> <htmlemail mailhost="smtp.blablablablabla.fr" reportsuccess="fixes" returnaddress="foo@blablablablabla.fr" subjectprefix="[CruiseControl]" skipusers="true" spamwhilebroken="true" xsldir="webapps/cruisecontrol/xsl" css="webapps/cruisecontrol/css/cruisecontrol.css"><br /> <always address="foo@blablablablabla.fr"><br /> <always address="bar@blablablablabla.fr"><br /> </htmlemail><br /> </publishers><br /> <br /> </project><br /></cruisecontrol><br /><br /><br />
For TSP the Ant build file was there to trigger the C build :
<br /><project name="tsp" default="build" basedir=".."><br /><br /> <property name="build.dir" value="tsp_cc_build"><br /> <property name="tsp.dir" value=".."><br /><br /> <macrodef name="cmake"><br /> <attribute name="flags" default=""><br /> <sequential><br /> <exec dir="${build.dir}" executable="cmake" failonerror="true"><br /> <arg line="@{flags} ${tsp.dir}"><br /> </exec><br /> </sequential><br /> </macrodef><br /><br /> <macrodef name="make"> <br /> <sequential><br /> <exec dir="${build.dir}" executable="make" failonerror="true"><br /> </sequential><br /> </macrodef> <br /><br /> <macrodef name="cvs-update"><br /> <attribute name="workDir"><br /> <sequential><br /> <exec dir="@{workDir}" executable="cvs" failonerror="true"><br /> <arg line="update -dP "><br /> </exec><br /> </sequential><br /> </macrodef><br /><br /> <target name="build" depends="update"><br /> <antcall target="vanilla"><br /> <antcall target="xmlrpc"><br /> </target><br /><br /> <target name="vanilla" depends="clean"><br /> <cmake/><br /> <make/><br /> </target><br /><br /> <target name="xmlrpc" depends="clean"><br /> <cmake flags="-DBUILD_XMLRPC=ON"><br /> <make/><br /> </target><br /><br /> <target name="clean"><br /> <delete dir="${build.dir}"><br /> <mkdir dir="${build.dir}"><br /> </target><br /><br /> <target name="update"><br /> <cvs-update workdir="${basedir}"><br /> </target><br /><br /></project><br /><br />
For TSP the setup instruction were :

• install a binary distribution of cruise control
• replace the config.xml file with the previous file. Change the email addresses of the 'returnaddress', and the 'always address'. You can add as many 'always address' as you want
• go to the 'projects' directory of the cruisecontrol install and perform an anonymous check out of tsp :

<br />cd projects<br />cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/tsp co tsp<br />
you can test the build without cruise control if Ant is available :
go to projects/tsp/make and launch :
<br />ant -f cc-build.xml<br />
If everything is OK, with the build, run the cruisecontrol.sh script. you're done,
cruisecontrol is up and running.