Click on the name of the share on the module's main page, then on the File Naming icon.

When the Case sensitive? field is set to No, the server will ignore case when opening files requested by clients. This is the way Windows filesystems work and so this is the default behavior for Samba, as well. It does, however, consume more CPU time and IO bandwidth due to the need to scan directories, as all UNIX filesystems are case sensitive. For this reason, you may want to select Yes if all your clients are Linux systems that expect normal the UNIX case rule to apply.

Normally, Samba will create files with the exact case specified by clients. To change this and force the use of upper or lower case instead, change the Preserve case? field to No and select one of the options in the Default case? field. This can be useful if Windows clients are creating lots of upper-case files when you prefer to follow the normal UNIX lower-case standard.

On Windows filesystems, each file has a hidden attribute that determines if it is normally visible to programs or not. No such attribute exists on UNIX systems. Instead, files whose names start with a dot are hidden by ls and other commands. For this reason, Samba sets the hidden attribute on dot files when the Hide dot files? field is set to Yes, as it is by default.

The alternative is to use the world execution bit of the UNIX file permissions as the hidden flag, as execute permissions are not otherwise used by Samba. To enable this behavior, change the Save DOS hidden flag? field to Yes. Because this will mess up permissions for UNIX programs accessing files in the share, it should only be used if the shared directory is only being accessed by SMB clients.

Windows files have two more attributes: the archive flag that indicates that a file has been backed up and the system flag that marks a normally untouchable system file. Samba can be configured to store these attributes in the user-execute and group-execute bits of files if the Save DOS archive flag? and Save DOS system flag? fields are set to Yes, respectively. If your Windows clients have no need for this information, or if you find that permissions on UNIX executables and scripts are being messed up, set them both to No instead.

To activate the new file naming settings, hit the Save button at the bottom of the page.