sudo apt-get install scalpel

It’s configuration is in /etc/scalpel/scalpel.conf. It offers some GPG related rules, but none for a revocation certificate. I used these rules:

revoc	y	100000	-----BEGIN\040PGP\040PUBLIC\040KEY\040BLOCK-----\x0aVersion:\040GnuPG\040v1.4.10\040(GNU/Linux)\x0aComment:\040A\040revocation\040certificate\040should\040follow
revoc	y	100000	-----BEGIN\040PGP\040PUBLIC\040KEY\040BLOCK-----\x0aVersion:\040GnuPG\040v1.4.9\040(GNU/Linux)\x0aComment:\040A\040revocation\040certificate\040should\040follow
revoc	y	100000	-----BEGIN\040PGP\040PUBLIC\040KEY\040BLOCK-----\x0aVersion:\040GnuPG\040v1.4.8\040(GNU/Linux)\x0aComment:\040A\040revocation\040certificate\040should\040follow

I wasn’t quite sure which version of GPG I had installed at the time I created the keys, so I created rules for all possible versions. (See manpage for syntax explanation.)
It took about 2 hours to scan the image of my 250 GB hard drive and scalpel successfully restored my revocation certificate.
I also tried some of the supplied rules but I think they are not suitable for restoring files from an image of a whole hard drive. (Most of them just look for two bytes that mark the beginning of the file.)

$ ruby test.rb sqlite3

                 user     system   total     real
insert           0.4500   0.0900   0.5400 (  7.303116)
find and update  0.4900   0.1400   0.6300 (  6.984390)
destroy          0.3300   0.1100   0.4400 (  7.261199)

$ jruby test.rb jdbcsqlite3

                 user     system   total     real
insert          17.2500   0.0000  17.2500 ( 17.250000)
find and update 16.3270   0.0000  16.3270 ( 16.327000)
destroy         15.0900   0.0000  15.0900 ( 15.089000)

$ jruby test.rb h2

                 user     system   total     real
insert           1.9320   0.0000   1.9320 (  1.932000)
find and update  0.7800   0.0000   0.7800 (  0.780000)
destroy          0.3180   0.0000   0.3180 (  0.318000)

That’s what I call an easy decision.

My setup can be downloaded here.

def method1(*args)
  puts "method1 got a block" if block_given?
end
 
def method2(*args)
  puts "method2 got a block" if block_given?
end
 
method1 method2 do
end
 
method1 method2 {
}

You would expect both method calls to produce the same result, wouldn’t you?
Output:

method1 got a block
method2 got a block

Obviously the do-end block is passed to the first method in the expression while the {} block is passed to the method called directly before it.
Another example shows that the assignment does not count as a method call here:

#[...]
class Foo
  def bar=(o)
    puts "Foo#bar= got a block" if block_given?
  end
end
foo = Foo.new
 
foo.bar = method1 method2 do
end 
#method1 got a block
 
foo.bar = method1 method2 {
} 
#method2 got a block

import dbus
 
bus = dbus.SystemBus()
 
proxy = bus.get_object("org.freedesktop.DeviceKit.Disks", 
                       "/org/freedesktop/DeviceKit/Disks")
iface = dbus.Interface(proxy, "org.freedesktop.DeviceKit.Disks")
#enumerates all devices
print iface.EnumerateDevices()
 
#gets the device kit path of a specific device
path = iface.FindDeviceByDeviceFile("/dev/sdc1") 
#= "/org/freedesktop/DeviceKit/Disks/devices/sdc"
 
#gets an object representing the device specified by the path
device = bus.get_object("org.freedesktop.DeviceKit.Disks", path) 
 
#prints some XML that shows you the available methods, signals and properties
print device.Introspect()
 
#gets a proxy for getting properties
device_prop = dbus.Interface(device, "org.freedesktop.DBus.Properties")
 
#you need to specify an interface (properties could be ambiguous)
print device_prop.Get("org.freedesktop.DeviceKit.Disks.Device", "device-mount-paths")
 
#gets a proxy you can call methods on
device_iface = dbus.Interface(device, "org.freedesktop.DeviceKit.Disks.Device")
 
#unmounts the partition
device_iface.FilesystemUnmount(dbus.Array([], 's'))

The DBus API of DeviceKit is documented here.
Now we want to be notified when a drive is mounted:

import dbus
import gobject
from dbus.mainloop.glib import DBusGMainLoop
 
def device_added_callback(device):
    print 'Device %s was added' % (device)
 
def device_changed_callback(device):
    print 'Device %s was changed' % (device)
 
#must be done before connecting to DBus
DBusGMainLoop(set_as_default=True)
 
bus = dbus.SystemBus()
 
proxy = bus.get_object("org.freedesktop.DeviceKit.Disks", 
                       "/org/freedesktop/DeviceKit/Disks")
iface = dbus.Interface(proxy, "org.freedesktop.DeviceKit.Disks")
 
#addes two signal listeners
iface.connect_to_signal('DeviceAdded', device_added_callback)
iface.connect_to_signal('DeviceChanged', device_changed_callback)
 
#start the main loop
mainloop = gobject.MainLoop()
mainloop.run()

A typical output when a flash drive is plugged in looks like this:

Device /org/freedesktop/DeviceKit/Disks/devices/sdc was added
Device /org/freedesktop/DeviceKit/Disks/devices/sdc1 was added
Device /org/freedesktop/DeviceKit/Disks/devices/sdc1 was changed

With this knowledge I’m currently working on a little python script that runs in background and executes a shell script when a file system is mounted. I’ll post it, when it’s finished

class A < Sequel::Model
  plugin :single_table_inheritance, :object_type
end
 
class B < A
end

The second argument is the name of the column to be used to store the class name in DB. Don’t use ‘type’ here, it collides with Ruby’s Object#type.
This works with version 3.5.0 and should work with any version >= 2.12.0.

manifest.rb:32:in `require': no such file to load -- monkeybars (LoadError)
	from manifest.rb:32
	from manifest.rb:21:in `require'
	from main.rb:21

To fix it, you got to change line 21 of manifest.rb:

add_to_classpath '../lib/java/monkeybars-1.0.2.jar'
#to
add_to_classpath '../lib/java/monkeybars-1.0.4.jar'

At 11.47 AM (local) I released the tow rope a little north western of Cham in about 700 m AGL (above ground level). My first thermal wasn’t good (or I just did not get it the right way). So I proceeded a little further north, lost some more height and found myself in weak, narrow thermal. I decided to drop my water ballast which probably was wrong. Afterwards the thermal improved and I could fly on to the north. Within the first hour I seldom was higher than 1000 m AGL. When I passed Weiden the altitude of the cloud base and the thermals’ strength improved and I got faster. The Fichtelgebirge provided me with some strong lift and soon I passed Kulmbach.

Sonneberg

Overhead Sonneberg I entered the Thuringian Forest. Some kilometers before Suhl I turned back southward. All in all I had to thermal too much for my taste on the first leg.

Bridge construction site on the Nuremberg–Erfurt high-speed railway

On the way back south I did a better job and did not thermal much until I was south of Tirschenreuth. A Janus joined me in close formation for some 40 Km. In order to stretch the flight a little I went on to the south east of Cham and turned near Bischofsmais.

From there I planned my final glide which was quite tight and got tighter due to some strong downdrafts in the area where I turned. But I was lucky and hit some thermals on the glide home. The second one was quite strong and I decided to gain any height I could get in order to make some extra kilometers. I again passed Cham and flew on to the north west. I could use some calm evening thermals, turned at Neunburg vorm Wald for the last time and went home fast.

With a distance of 529 Km and a duration of 6 hours and 37 minutes this was my farthest and longest flight. Because of the high amount of traffic and the sometimes rough thermals I only took a few pictures today.

Here is the flight on the OLC.

massage passing as means of coordination

One should try massaging each other to improve a team’s coordination.

./script/generate model Thing a:datetime b:datetime

My model:

class Thing < ActiveRecord::Base
  def b=(d)
    write_attribute(:b, d)
  end
end

My tests:

require 'test_helper'
 
class ThingTest < ActiveSupport::TestCase
  test "a and b" do
    d = DateTime.now
    t = Thing.new
    t.a = d
    t.b = d
    t.save
    assert_equal t.a, t.b
    t.reload
    assert_equal t.a, t.b
  end
end

The second assertion will fail. Is this intended or a bug?
Quick fix:

  def b=(d)
    d = d.utc
    write_attribute(:b, d)
  end