Well to start with some device-mapper basics, looks at the newer files (e.g. thin-provisioning.txt, cache.txt) in the Documentation directory to see what format to use and how to document the interface. Constructor, status, examples using dmsetup only etc. (BTW We don't use equals signs in our interfaces.) But even before any of that, I'm puzzled by the basics of how this can have been fitted into a device-mapper interface where the "sine qua non" resume function is still TODO, 'dmsetup table' appears unimplemented, 'status' doesn't appear to provide the internal status, and 'load' has some keywords that also don't appear to fit. Look at how the existing dm targets divide up the work between each of the functions and model your interface on those. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
