Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using a Linux server as fileshare. These files are accessed by Windows computers with a Samba server, accessed by Macs with a netatalk server (afpd) and also trough ssh an sftp for Windows, Macs and Linux system.

It seems like some of these systems care about the use of characters in filenames and some don't..

There is a tool called 'convmv' to convert filenames from one to another, but which one should I use?

Should I setup the Samba server for a defined file encoding? Same for netatalk?

share|improve this question

migrated from Apr 28 '10 at 14:42

This question came from our site for professional and enthusiast programmers.

the only sane encoding is UTF-8. for everything. – Javier Apr 28 '10 at 15:18

No, you shouldn't setup a specific filesystem in samba.

Linux usually uses UTF-8. You should use that. Samba negotiates automatically with it's clients the encoding and converts the filenames on the fly.

I have no idea regarding netatalk, but it shouldn't be necessary.

Regarding sftp, simply don't use it for windows. Windows assumes that files will be encoded with an encoding like codepage 1252. Use samba that will do the needed conversions on the fly and you'll save yourself a lot of problems.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.