Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ Performance and implementation notes:

libmtp (and I assume the MTP protocol itself) doesn't support seeking within a
file or partial file reads or writes. You have to fetch or send the entire
file. To simluate normal random access files, when a file is opened the entire
file. To simulate normal random access files, when a file is opened the entire
file contents are copied from the device to a temporary file. Reads and writes
then operate on the temporary file. When the file is closed (or if a flush or
fsync occurs) then if a write has occurred since the file was last opened the
Expand All @@ -88,7 +88,7 @@ writing it back to the device under the new name, and then deleting the
original file. This makes renames, especially for large files, slow. This
has special significance when using rsync to copy files to the device. Rsync
copies to a temporary file, and then when the copy is complete it renames the
temporary file to the real filename. So when rsyncing to a jmtpfs filessystem,
temporary file to the real filename. So when rsyncing to a jmtpfs filesystem,
for each file, the data gets copied to the device, read back, and then copied
to the device again. There is a true rename (but not move) supported by libmtp,
but this appears to confuse some Android apps, so I don't use it. Image files,
Expand Down