very interested to see if that works.
The biggest feature request I could ever ask for is a better way of resolving the image files.
Right now for one image:
win2k3entx86
win2k3entx86.000
win2k3entx86.001
win2k3entx86.002
win2k3entx86.first_sectors
win2k3entx86.part
I have to create all these hardlinks:
/win2k3entx86-ide/hda
/win2k3entx86-ide/hda1.000
/win2k3entx86-ide/hda1.001
/win2k3entx86-ide/hda1.002
/win2k3entx86-ide/hda1.first_sectors
/win2k3entx86-ide/hda.part
/win2k3entx86-sda/sda
/win2k3entx86-sda/sda1.000
/win2k3entx86-sda/sda1.001
/win2k3entx86-sda/sda1.002
/win2k3entx86-sda/sda1.first_sectors
/win2k3entx86-sda/sda.part
/win2k3entx86-sda/cciss/c0d0
/win2k3entx86-sda/cciss/c0d0p1.000
/win2k3entx86-sda/cciss/c0d0p1.001
/win2k3entx86-sda/cciss/c0d0p1.002
/win2k3entx86-sda/cciss/c0d0p1.first_sectors
/win2k3entx86-sda/cciss/c0d0.part
x 6 image types = 108 hardlinks
If there was only a way to detect the primary disk type and then resolve one set of files instead of having 3 sets for each.
