Writing to USB stick - (Caja) non-sync'ed?

May I bring to your attention an observation and expectation regarding Caja behaviour, which I have posted on another site?

Would it be possible to modify Caja code to only report “Copy/Move/Delete completed” after the last block of the last file involved in the operation is confirmed as physically where it needs to be (or not)?

Or is that physically outside of the scope of the MATE-captive Caja source code?

1 Like

I think I understand what you want and why you want it. In mkusb I have a small tool, watch-flush that not only runs sync after copying big files like Ubuntu family iso files, but it also shows the progress when flushing the buffer via zenity.

A simple solution is to make a shellscript, that would run cp (with parameters) and then sync instead of running ‘only’ cp. Then you should wait until the terminal returns to prompt. You could even add for example

espeak 'I am ready now'

into the shellscript after the sync command.

The reason why I suggest a shellscript is that it is much easier to make and test, and when you have something that is working well, you can try to make the maintainer(s) of Caja interested.

5 Likes

@ericmarceau it is a good observation and as a regular user I agree with you. My suggestion however would be to raise an issue upstream with a ‘feature-request’ tag.

6 Likes

I did that earlier, but forgot to post the link:

5 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.