When I was just about ready to give up I plugged in the HDMI cable again and saw a strange libcrypt error show up. I even managed to generate a kernel panic once! Sh: can't access tty job control turned off I tried various cmdline.txt changes, I saw an odd message saying: When I plugged a keyboard and HDMI cable in the login would fail silently at first and then after reboot it would tell me the password was wrong.įearing the worst, that the small machine had been hacked, I plugged it out and attempted to go into single user mode but even that didn’t work. When I ssh into it the password is rejected. Rather, one should always use -iconv=utf-8-mac,utf-8 when initialising the rsync from the mac, and always use -iconv=utf-8,utf-8-mac when initialising the rsync from the linux machine, no matter if I want to sync files from the mac or linux machine.ĮDIT: Indeed, sometimes, checking the manual page closely is a good thing to do. The solution was embarrassingly simple: Much due to a comment I read when researching the problem, I thought you were supposed to specify the character set in the order of transformation but it seems as that is not the correct syntax. Rsync has an option named -iconv to convert between character sets! The solution took a while for me to find but it’s very simple. A file with an accented character on the Mac is completely different to one that looks the same on the Linux box. It turns out the Mac and Linux machines I’m using have different ideas about character sets their filenames are stored in. I thought it worked fine until I quickly realised it was syncing the same files over and over again.
Too large to run Syncthing on it unfortunately, but an occasional rsync is perfectly fine.
I have Plex running on a Raspberry Pi for my music. 99.999999% of my readers can probably ignore this one, but if you are of the small minority who use Rsync and have Mac and Linux computers in your home you’ll want to read this.
0 kommentar(er)
