As no answer has (yet) been given,
I would like to rewrite differently my
thoughts :
I want to give a simple user the ability the do
something when a block subsystem event happens.
1) with udev it means using libudev and rewriting a udev subset
2) with hal it means "hook"ing a helper in a policy
As a precision :
dbus_g_proxy_call() returns 0 but hash_table contains 0
entry.
It's maybe related to the fact that
props->device_file_by_id[n]
and
props->device_file_by_path[n]
are NULL => segfault
the "for" loop should probably contains something like :
props->device_file_by_id != NULL
and
props
If you want any patches / fixes included for the release then you've
got a few days left for review. Testing especially welcome.
If you're expecting DeviceKit-power to work on Solaris or FreeBSD in
future releases, there's a framework in place just waiting to be used.
Hint hint.
Richard.
