Add write back support for unmount option and copy to support for mount option

[psdzzm]

Add a -c, --copy-back option for the unmount operation.

Achieved by using cp instead of std::fs::copy, because cargo uses the file timestamps to determine if a file has changed.

[psdzzm]

Also add copy to ramdisk option for the mount operation, using c, --copy-to option

[PauMAVA]

Hello! @psdzzm

First of all sorry for the delay in my response to your PR. I think it's a great addition to this project. I have noted a couple of small fixes about logging. When you fix them I will proceed to run the workflow and merge this into the main branch.

Also, could you add a test case for copy_to and copy_back?

Thanks a lot for your contribution and interest in this project! 😄

[psdzzm]

Hi @PauMAVA
I'm sorry for not getting back to you sooner. I've resolved the logging problem and added a test for copying to and back.

cargo-ramdisk/src/main.rs

Line 287 in af865ab

fn test_copy_back() {

[PauMAVA]

Hey!

No problem. Almost there, please run cargo fmt and commit the changes so that the workflow doesn't fail.

Thanks!

[PauMAVA]

Everything good!

Thanks a lot for your interest and contribution to cargo-ramdisk @psdzzm 😄

[PauMAVA]

Available in crates.io as from 0.2.0.

[psdzzm]

If possible, you can add the copy to and back option in README. Both mount and remount use -c option for enabling, like cargo ramdisk mount -c.

[PauMAVA]

Yep. Just updated the README and also the workflow as the tests were failing sometimes due to test parallelism.