The only mac file character I think it *might* choke on is embedded carriage returns in a filename. # tar -cf - * | ssh "( cd destdir tar -xpvf - )" You can use other special characters such as blank space, but they are hard to use and it is better to avoid them. # cd (parent directory of what you want to transfer) You can use upper and lowercase letters, numbers. Unfortunately, pretty much the only ongoing solution is to slap users who try to contribute files with non-Windows-compatible filenames, if samba's your filesharing poison of choice.įor reference, here's my favorite way of transferring huge wads of files between unixoid systems: srt to process every file) Removes all other characters except for letters A-Za-z, numbers 0-9, periods '. # cp \ This\ is\ an\ evil\ filename\:\\ \!\ \*\ #\ \ \ \? /mnt/Ĭp: cannot create regular file `/mnt/ This is an evil filename: ! * # ?': No such file or directory # mount -t smbfs -o username=whoever //otherserver/share /mnt This is with smbclient, to show the error, but it doesn't work if you do this either: NT_STATUS_OBJECT_NAME_INVALID opening remote file \ This is an evil filename:! * # ? Put file This is an evil filename: ! * # ? y Try copying it to a Samba server, however, and: # touch " This is an evil filename: ! * # ? The problem is that such characters break shell expansions, pipes, etc, etc. I'm pretty sure you can use *any* UTF8 character in a Linux filename. Also, using another protocol wouldn't work because the characters are illegal for the destination filesystem
0 kommentar(er)
