> On Sep 1, 2016 08:40, "Michael" wrote: >> bmike1@MikesBeast ~ $ rsync -aWuq --delete-before >> /home/bmike1/Documents /media/bmike1/RedSanDisk >> rsync: mkstemp >> "/media/bmike1/RedSanDisk/Documents/Business/Photography/PropertyPhotographing >> /PrivateClients/Carmen Bongiovani/2016/20160728/.11 Wedgewood >> Ln,#012Palm Coast, FL 32164.54RzTX" >> failed: Invalid argument (22) >> I'm so pleased with myself! I noticed the forward slash and the #012 >> and I figured  I had pressed while naming the file >>  (must be the line feed character) and that #012 is the ascii >> character >> for a space \n is 012 (10 0x0a) while space is 040 / 32 / 0x20. \n is a legal character for filenames in the ext234 filesystems, so this backup disk must be FAT or NTFS. Usually, things will be easier if you make your filenames match /[A-Za-z0-9_\.-]+/ because those characters are valid on all commonly used filesystems. On 2016-09-01 08:41, Anon Anon wrote: > ABC always be camelcase. Nbs never be spacing CamelCaseCanBeTakenToStupidExtremesAsSeenInALotOfBloodyJavaCodeSoDontDoThat. People use spaces in filenames because they never think about how spaces make command-line processing of files more annoying, but then not many people do a lot of handling files on the command line these days. -- Crow202 Blog: http://crow202.org/wordpress There is no Darkness in Eternity But only Light too dim for us to see. --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: http://lists.phxlinux.org/mailman/listinfo/plug-discuss