MavEtJu's Distorted View of the World - 2013-07Back to index Some kind of image viewer...Posted on 2013-07-15 08:00:00 I am looking for some kind of image viewer... Wow, great description :-) The background is that I need a way to collect and manipulate various images, screenshots of graphs of other applications like Wireshark and various other graphers, and then be able to easily resize these images (so the size of the data matches the size of the data of the other images) and move them around on the area. So I need an infinite zoomable canvas with on it freely resizeable and freely moveable image objects. If you know anything like this, and preferably cross-platform, please let me know!
Scared!Posted on 2013-07-11 08:00:00 The website reddit.com, self-proclaimed "Front page of the Internet", has one section which I like to visit while bringing my kids to bed: The [[//www.reddit.com/r/AskReddit/][Ask Reddit] section, in which people post their comments on a certain subject. There are a lot of shitty questions which you can ask, but due to the moderation system I only get served the highly rated ones, plus if the subject of the question doesn't interest me I don't bother to read it. Yesterday the one I read was "What's a story that you've heard that still gives you chills to this day?". Most of them are real-life stories and some made-up-to-scary-teenagers ones. This one particularly stuck with me, but didn't scare me when I was reading it last night:
A kid is playing in his room, when he hears his mother call him from the kitchen. He puts down his toys and walks down the stairs, when suddenly upstairs he sees his mother who says "Don't go there, I heard that voice as well." Typical sitting-around-the-fire-and-scaring-each-other-story and it didn't bother me last night. This early morning at 06:00, still dark, while hanging up the washing, I hear a sound behind the bins which are standing in the dark corner of the garden about three meters away from me. And the only thought that my scumbag brain could come up with was "I heard that sound as well."... Needless to say that I wasn't feeling happy anymore.
I got a medal!Posted on 2013-07-10 08:01:00 Last night the Safe Sets team finished as second in the Miranda Indoor Sports Center after two sets of 21-25 and 19-25. Team Cannonfodder became first and got a trophy, we got medal. First medal after nearly three years of playing. Yay me! :-)
Sawtooth on a Raspberry PiPosted on 2013-07-08 08:00:00 Recently I have obtained two Raspberry Pi units, just to see what can be done with them. So far I'm impressed, this little device is pretty powerful with regarding to video. Being a network guy, this doesn't interests me very much. But as a replacement of a 150 dollar Serial-over-TCP unit it would be very handy to get a serial console on devices it is required for. First thing, this device runs with an ARM processor, something I haven't played with before on system administration level. First I had to build a FreeBSD ARM based kernel and world and that failed dramatically on my FreeBSD 9.1 i386 based machines. So VirtualBox to the rescue, and on an 64 bit machine it compiled a 10-Current world. My first cross-build was successful! This disk for the Raspberry Pi is just a flash card, so I had to build an boot image (that was easy), download it to the host of the VirtualBox service (that was easy) and tell somehow OSX to not mount the disk anymore but also to keep it available for me to use dd on. That was tricky, but nothing Google couldn't tell me. Then the final moment: Boot the Raspberry Pi with FreeBSD and... It worked. How undramatic. Ping the router, ping something on the Internet. All fine. Except that the RTT for the ICMP packets didn't make sense: 64 bytes from 192.168.123.231: icmp_seq=22 ttl=64 time=1.321 ms 64 bytes from 192.168.123.231: icmp_seq=23 ttl=64 time=10.312 ms 64 bytes from 192.168.123.231: icmp_seq=24 ttl=64 time=9.328 ms 64 bytes from 192.168.123.231: icmp_seq=25 ttl=64 time=8.335 ms 64 bytes from 192.168.123.231: icmp_seq=26 ttl=64 time=7.411 ms 64 bytes from 192.168.123.231: icmp_seq=27 ttl=64 time=6.448 ms 64 bytes from 192.168.123.231: icmp_seq=28 ttl=64 time=5.497 ms 64 bytes from 192.168.123.231: icmp_seq=29 ttl=64 time=4.508 ms 64 bytes from 192.168.123.231: icmp_seq=30 ttl=64 time=3.540 ms 64 bytes from 192.168.123.231: icmp_seq=31 ttl=64 time=2.588 ms 64 bytes from 192.168.123.231: icmp_seq=32 ttl=64 time=1.635 ms 64 bytes from 192.168.123.231: icmp_seq=33 ttl=64 time=0.738 ms 64 bytes from 192.168.123.231: icmp_seq=34 ttl=64 time=9.770 ms 64 bytes from 192.168.123.231: icmp_seq=35 ttl=64 time=8.805 ms 64 bytes from 192.168.123.231: icmp_seq=36 ttl=64 time=7.833 ms 64 bytes from 192.168.123.231: icmp_seq=37 ttl=64 time=6.843 ms 64 bytes from 192.168.123.231: icmp_seq=38 ttl=64 time=5.869 ms That is a beautiful sawtooth, but that doesn't make sense. I tried various things, like setting the tick interval from 100 to 1000 Hz, but no luck yet. Together with Peter Jeremy we are looking for an answer, but being a non-kernel guy there is not much what I can do here except test patches. |