Hi all,

quick update for today.

I replaced the CSS used from ui-darkness to vader, it looks a bit cleaner. I was thinking that probably in the future would be nice to add a theme selector somewhere 😉

Also, I changed the way disks are labeled in dwipe, so it actually doesn’t need anymore the .label file to start, but it will automatically get the model of the device from HDIO_GET_IDENTITY or from /sys/class/block/DEVICE_NAME/device/model if the file exists.

The new format of label is :

/dev/ – DEVICE_MODEL

So, for example :

/dev/sda – VBOX HARDDISK

During this week I will also spend some time to build a micro distro for Disk Nukem (still thinking about whether to use a custom or building from existing ones) and release an ISO / netboot image so people can start to play around with it.

Cheers !

Hi,

today I added three new options that allow to notify a remote system of what is happening to the machine while is performing the disk wiping:

1. –notify-start : fetches a URL when the actual wipe starts
2. –notify-fail : fetches a URL when a failure occurs
3. –notify-success : fetches a URL when the wiping completes w/o errors

There is to say that notify-fail might not be called if dwipe actually crashes, so no one will be informed of the crash.

I will think about this next week, although it makes much more sense to test the error code on exit (but then the notify-start needs to be adjusted to run before launching dwipe), that translates to wrap dwipe’s launch into a small bash script file.

If this will be the case, then the notify options won’t be available when launching dwipe in standalone mode (and actually this is one of the future features).

Alternatively, a master process might just monitor and talk to dwipe and send only the notifications when needed.

If anyone out there is having a better idea or has opinions, just shout it!

I’m off for next day 🙂