betabug... Sascha Welter

home english | home deutsch | Site Map | Sascha | Kontakt | Pro | Weblog | Wiki

11 June 2014

The site is coming back

Not all those who wander are lost

On the 24th of February my server had crashed hard. At first all was gone. Then some backups turned out to be well and kicking... but another important backup turned out to be an emtpy shell of a tarball. Years of data were gone. Nothing too important, nothing too personal.

I got the server's hard disk back, but with the information that it spins up, but the controller doesn't answer. I put it in a drawer and tried to forget about it. I put off fully restoring my site for a while, because I was busy and because it just wasn't a feel-good task.

Last saturday I hooked up the disk with an adapter to my laptop. The controller answered just fine, I could "see" the partitions. I still needed a PowerPC machine to boot the OpenBSD/macppc on the disk. I remembered that there was such a box in the hackerspace in Athens. Went there, booted the disk (worked just fine). It took me a while to get the data off it, because the system wouldn't let me log in from the console. Booting into single user worked, and getting minimal networking up worked too.

I now have my stuff on the laptop, and I'll be restoring more and more stuff as I get to it. You alreayd see the pictures are back at this weblog and the imagelog works again too. Plenty busy at work, so it still might take some time. But it's all there, and that lets me take a big sigh.


Posted by betabug at 14:17 | Comments (0) | Trackbacks (0)
13 June 2014

Getting into the Ruby Debugger

The missing fin

I was trying to debug a ruby script yesterday, so I searched the docs and the web for how to do this. Part one of the problem: various older versions had different ways to do this, having to install some gem or not, etc. Ruby 2.1 has something built in, so there I was. Put this in your code:

require "debug"

Simple enough (in Python it's "import pdb; pdb.set_trace()"). But then I got stuck, because the debugger was somewhere in the debugging code, not in my code. No mention of that in the docs or in the tutorials I'd found.

The solution was to step up from the current frame, with the debugger command:

fin

which is short for fin[ish] - return to outer frame. The h command gives all the help you need - as long as you are used to command line debuggers like Python's pdb. But that fin thing had me searching and wondering for a while.


Posted by betabug at 13:36 | Comments (2) | Trackbacks (0)