Scripting a ssh tunnel
Sometimes I wonder why I put up with some inconveniences in my work flow. One particular issue I have for a long time is working with ssh-tunnels. It always goes like this: I start a ssh tunnel or other proxy, run a program that uses this proxy and use it until I am done with it, and finally close the proxy afterwards. For a long time I was doing this manually using a terminal, until I finally got fed up with the tedious routine and wrote this simple bash script:
code:
Read more »
code:
1
2
3
4
| #!/bin/sh /usr/bin/ssh -N -D 3124 username@localhost & # Enter your program here kill $! |
Read more »
Fighting for privacy?
Last week I had the pleasure of discussing my viewpoints about privacy with one of my house mates. One particular remark of her remained stuck in the back of my head, leaving me wondering about the validity and consequences of it: 'We will lose eventually, and there is nothing we can do about it. So why should we even resist?'.
Read more »
Read more »
Rabbit's Revenge
Last month (30th of May, to be precise), the Blender Peach Project published its movie online. Ten days before that enthusiasts could already order the dvd of this second Open Movie, but odds are that most of the community was probably rooting for the online event. I saw the movie yesterday and, since it was apparently missed by the t.net news queue, I thought I should give it some love. And believe me, the movie deserves it.
Read more »
Read more »
Cleaning up version-controlled directories
When writing LaTeX documents, you often end up with all kinds of redundant files. These files are generated during the compilation of a dvi or a pdf document and can generally be discarded afterwards. Most of my tex documents are under version control and, consequently, it is possible to get a list of the files that are (and are not) under this control. Using a single Bash command, you can abuse subversion to determine which files you want to delete:
Read more »
rm -i `svn status | awk '/^\?/ {print $2}'`Read more »
Saxion en CAA, losmakelijk verbonden 
Zoals ik al eerder schreef, was boterde het niet lekker tussen het door CAA-beveiligde netwerk van het Saxion en Linux-gebruikers. Servers die toegankelijk waren via het Internet werden afgeschermd voor het interne netwerk en Linux-gebruikers werden min of meer gedwongen om door allerlei hoepels te springen om hun werk normaal te doen. Sinds kort niet meer: de weg naar de schoolwebsites, de Subversion-server en de Linux-systemen is twee dagen geleden vrijgemaakt voor Saxion-gebruikers zonder CAA
.
Lees verder »
Lees verder »