Where have I been?

This is pretty cool...



create your own visited states map

A Challenge

I often wonder if the number of hopeful days balance out the number of hopeless days. Has anybody ever tried writing down how they feel each day and doing an analysis on it? The patterns one finds could prove very interesting. And why does hopeful only have one L?

Random Thought

It is interesting and disturbing how few quiet places there are in my world. The loss of power always seems to leave a ringing in my ear...

Partition Fun

I recently made the mistake of installing Linux on a single disk partition. As a result, my home directory and all of my settings were stored on this partition and I was long past due for an OS upgrade. Luckily, a utility called RESIZE2FS for resizing EXT2/3 filesystems exists. With this tool, I was able to shrink the root filesystem from its original 60GB size down to approximately 20GB:

resize2fs -p /dev/sda1 20G

At this point, I could manipulate the partition table, resizing the first partition to 20GB and creating a new partition which would serve as my /home folder in the unused space. As long as the first partition is large enough to encompass the root filesystem, this should not cause any problems.

Finally, I could create a new filesystem in the new partition and copy my home directory there:

mke2fs -J /dev/sda2

At this point, I can install a fresh OS, formatting the root filesystem and still preserve my user settings :)

Sometimes print is bad

I wrote a simple Ruby script that, given a connection request on a particular port, opens a connection to a remote host on a particular port and forwards all packets from one to the other, a very simple packet forwarder. For debugging purposes, I was printing some text to standard out for each packet received / forwarded. I set up a simple performance test running the forwarder on my local system and generating packets using /dev/zero...something like this:

ruby forwarder.rb 20000 10000 localhost

nc -l -p 10000 -c "cat /dev/zero"

nc localhost 20000 > moo

After running this test for 15 seconds, the output file "moo" reached a size of 48MB on my laptop, indicating a throughput of over 3 MBps. Although this was sufficient for my purposes, it was much lower than I expected given that transfer should only be limited by the speed of my laptop harddrive in writing the output file.

By simply removing all "puts" calls for output, the performance increased dramatically. With the same 15 second run, the output file "moo" reached a size of 350MB on my laptop, indicating a throughput of over 23 MBps!

I suppose that when writing an application that handles a large amount of data, all debugging should obviously be turned off. However, it wasnt obvious to me that it could have such a large impact on performance. Hopefully this will help me not make the same mistake in the future.

Ruby Trix

I've been having a number of problems in Ruby of late with error handling in Threads. In particular, any time I encounter a problem in a thread, I was given no indication that something went wrong.  It turns out that by default, an unhandled exception simply kills the current thread and you don't even hear about it unless you issue a "join" on the thread that raised the exception.  I suppose proper coding practice would be to handle my exceptions appropriately, but for debugging, it is nice to know when something has gone wrong.  The simple snippet of code:

Thread.abort_on_exception = true

takes care of this problem.  With this modification, any unhandled exception kills all running threads and yields readable error information.

Don't Fall In

Shocking proof that women, and even some men are afraid to admit that they go number 2...

http://news.bbc.co.uk/2/hi/health/6128738.stm

I wonder what they did in the olden days before bathroom stalls offering doors and some semblance of privacy existed?  Not only that, but what does this say about other things these people might be hiding from themselves and others?  Denail and self-consciousness knows no bounds.