A cautionary demo using SAMBA and YASSM
Suppose/imagine, that the transferred directory used in the demo is one of many which you move temporarily so that you can later get them back (using SAMBA and YASSM again ).
The set up:
2 computers with wired LAN connection.
Computer 1 (initial host) running Friendly-Fossa64.
Computer 2 running in turn Friendly-Fossa64, JammyPup32 and Book Worm-10.0.3
Step 1:
Using SAMBA and YASSM, transfer the directory (contents) ~/my-documents/tmp/Umlaute from computer 1 to computer 2. The directory contains 2 files, Zürich.pdf and Zürich.odt, both are valid UTF-8 file names.
Step2:
On computer 2 copy the transferred directory from ~/YASSM to ~/my-documents/tmp/dir.
Then close YASSM and instead set up a SAMBA share for ~/my-documents/tmp/dir.
Step3:
On computer 1, use YASSM to transfer ~/my-documents/tmp/dir from computer 2.
What happens:
(Step 1)
- with Friendly-Fossa64 and JammyPup32, the transferred files become non-valid UTF-8.
Zürich.odt opens with AbiWord; Zürich.pdf opens with Evince pdf viewer in JammyPup32 but fails to open with qpdfview in Friendly-Fossa64.
The lower part of the screenshot below is from a Gtk-dialogue.
- transferred_JammyPup32.jpg (61.31 KiB) Viewed 258 times
- With Book Worm-10.0.3, the transferred files are valid UTF-8 and open with their respective applications.
What happens:
(Step 3)
- With Friendly-Fossa64 and JammyPup32, YASSM does not show any files having been transferred.
In effect, the files have been lost! (gone to oblivion)
- step3-oblivion-(JammyPup32).jpg (53.26 KiB) Viewed 258 times
- With Book Worm-10.0.3, the transferred files become non-valid UTF-8.
- step3-transforming-(BookWorm10.0.3).jpg (70.34 KiB) Viewed 258 times
YASSM v4.5 and YASSM v4.1:
Book Worm-10.0.3 uses YASSM v4.5, while Friendly-Fossa64 and JammyPup32 use YASSM v4.1.
YASSM v4.5 pets are available for Fossa64 and JammyPup32.
Thinking that perhaps v4.5 would make a difference, I installed the pets, but that had no effect.
So it seems something else (than v4.5) in Book Worm-10.0.3 allows it to correctly handle YASSM share mounts of files with Umlaute in their name.
YASSM's handling of files with Umlaute in their name is of concern to me. I have an Umlaut in my surname.
Luckily here is an alternative that can be used with such files (even non-valid UTF-8 ones !): PureFTPd together with gFTP.