It is often pointed out that the several pre/post operations in create/remove is not easy to understand such as
The cache device should be zeroed out the first sector to reformat in dmsetup craete
The integer preceding the k-v optional pairs should be multiple of 2
User should do suspend then resume magic to flush the dirties on the RAM buffer
wbcreate and wbremove hide these knowledges.
In my opinion, it would be better to not allow users to touch dmsetup create and remove but encourage them to use wbcreate and wbremove instead so they don't need to read README.
Now I wonder if I need to keep the documentation about dmsetup or remove them all and just say "Use dm-writeboost-tools"
I've created dm-writeboost-tools which makes it quite easy to create/remove writeboost devices.
https://github.com/akiradeveloper/dm-writeboost-tools
It is often pointed out that the several pre/post operations in create/remove is not easy to understand such as
wbcreate and wbremove hide these knowledges.
In my opinion, it would be better to not allow users to touch dmsetup create and remove but encourage them to use wbcreate and wbremove instead so they don't need to read README.
Now I wonder if I need to keep the documentation about dmsetup or remove them all and just say "Use dm-writeboost-tools"