sadevil.org

You know what I really hate? Crap parkers. People that have a car, and that, according to them, needs to take up atleast 1.5 parking spots. Parking so badly that you - parked nicely in between the lines, in the bloody center - can’t get in or out of your car anymore, save by crawling in the car over the seats.

Lately we’ve been encountering more and more of these idiots, so we’re starting a new category: the crap parkers.

Here’s the first (ok, not _that_ crap, but it was crap enough that I couldn’t get in anymore the regular way) - car on the left:

Simon’s Cat YouTube channel

Read more »

Here’s a short how-to to get the iodine dns tunnel working on your Mac.

In this short howto, I’ll assume you’ll be using a linux server to act as your gateway to the world. I’ll also assume you’ve read the iodine documentation and setup your DNS accordingly. For my example, I’ll be using a (nonexistant) DynDNS.org static DNS entry, iodine.rulestheworld.tld. I’ll also assume that you’ll be using a public internet address of 1.2.3.4, and a private subnet of 10.0.0.1.

1. Install the tun/tap driver for Mac OS X. Easy as doing *click* *click* done! :p
2. Next, install iodine on your Mac. Easy as download, extract, and typing make; make install
3. Now, install iodine on your linux box. It’s included in the package repositories of the usual suspects, for instance debian: apt-get install iodine.

   Start it (or configure it to use) with:
   iodined -P <password> <unused private IP> <dns name>
   or in our example:
   iodined -P mypass 10.0.0.1 iodine.rulestheworld.tld

   This should return the following:

   Opened dns0
   Setting IP of dns0 to 10.0.0.1
   Setting MTU of dns0 to 1024
   Opened UDP socket
   Listening to dns for domain iodine.rulestheworld.tld

4. Configure your linux box for IP forwarding: sysctl -e net.ipv4.ip_forward=1
(and add this to your /etc/sysctl.conf file), and configuring your firewall (iptables) for masquerading:
   iptables -t nat -A POSTROUTING -s 10.0.0.0/255.255.255.0 -o eth0 -j MASQUERADE
5. Next, download NStun.sh, a very handy script that does all the hard work of changing the routes and so on :p

   You’ll want to change the script: change the first lines as the script reads, and lower, change the
   

   NS=`grep nameserver /etc/resolv.conf|head -1|awk ‘{print $2}’`

   line to read

   NS=”62.213.207.197″

Now, start NStun.sh on your Mac, and surf away! (well, slowly, but freely, atleast!)

I was trying to get xrdp running on my Linux box, so I could takeover the screen from the outside world. The rdp protocol is a (huge) bit more performant than VNC, which is why I wanted to use it.

Today I was trying for the 3rd time to get it to work, using CoRD as an RDP client, but I never got any image back - the client started, I saw the connection being built up, but I never got any image over. Starting rdesktop locally gave me the output I expected.

This gave me the idea of using Microsoft Remote Desktop Connection Client for Mac 2 Public Beta, to see if it might be a problem with the client… and yup, it is.

Seems CoRD 0.4.3 (the current stable) is unable to handle the output of xrdp. I now installed the 0.5 beta 1 which works without any problems.

I got a company phone, a Nokia 3109 Classic, which is nothing less nothing more than a standard company phone. It doesn’t have all the bells and whistles I’d like to have, but it works.

What didn’t work, was iSync on this phone. Real bummer, since I was hoping to sync everything between iCal/Address Book and this phone…

Google to the rescue, and i stumbled over this blog posting by James Lloyd, detailing how to get it to work.

Summary:

1. Download the script here
2. Right click iSync from the Applications folder in Finder and choose “Show Package Contents”
3. Navigate to: Contents\Plugins\ApplePhoneConduit.syncdevice\Contents\Plugins\Nokia-6131.phoneplugin and choose “Show Package Contents” again.
4. Navigate to \Contents\Resources
5. Replace the content of the MetaClasses.plist file with the content of the script downloaded in step 1
6. (Re-)Setup your phone with your Mac

Done!

This is not a good weekend. For me atleast…

• Yesterday, an upgrade at work took longer than expected. Hence, had to call of external testing parties. Today I had to call them again, but most were not available. Joy for tomorrow.
• Yesterday, windows decided to eat a partition which was on a Dynamic Disk. Scanned it today with GetDataBack, but only got half of my stuff back. No joy.
• For some reason, parts of my linux installation broke themselves. No joy.
• This morning, yet another thing broke at work, for obscure reasons. Even less joy.

Can this weekend be over and done already?

If you want to copy a bunch of files from one spot to another, but preserve links/permissions/ownership/…, it’s usually a big hassle.

With tar, you can make this hassle disappear!

Copying a directory tree and its contents to another filesystem using tar will preserve ownership, permissions, and timestamps. You can use pipe tar to another tar to prevent having to create an intermediate file to store the stuff you want to copy around.

To copy all of the files and subdirectories in the current working directory to the directory /destination, use:

tar cf - * | ( cd /destination; tar xfp -)

The first part of the command - tar - makes a tarball of all the files, and writes this to stdout. The second part of the command part will first change directory, and then extract the tarball in that location, reading from it’s stdin.

Since the cd and tar commands are contained within parentheses, their actions are performed together.

The p option in the tar command instructs tar to preserve the permission and ownership information, if possible. So if you want to move a lot of files around, it’s advisable to do so with the root user to keep all them permissions!