Bad Names

Another form of file lint is bad file names. These files may not eat away at hard drive space, but they may be difficult to use or move. The common user will occasionally encounter bad names when they try to copy their music collection from their computer to their portable device. This can result in odd warnings about a file having an invalid name, and the transfer fails. Typically this is found when the file was titled in a language other than the user's native language. While bad names are a common annoyance, it is not required that the user fix them (though it is recommended).

 Graphical Interface

 

'Bad names' searches out all files and inspects their naming conventions. The slider at the top of the section allows the user to set the sensitivity level. Level one is the least strict while level four is a strict POSIX check. The check box to the right of the slide bar allows the user to select UTF8 checking. The color code is simply the color given by the 'ls' command on the users system. Please consult the OS help pages for more information on UTF8, POSIX, and 'ls'. 

Command Line Interface

There are two utilities provided by FSlint for command line checking. The first is 'findnl' to find bad names. The second is 'findu8' to find names with bad UTF8 encoding.

findnl

 $ /usr/share/fslint/fslint/findnl --help
  find Name (directory or file) Lint.
  Usage: findnl [-1] [-2] [-3] [-p] [[-r] [-f] paths(s) ...]

  These options are mutually exclusive (i.e. only the last one takes effect).
  -1 is least checking, -3 is most. The default is 2.

  -p is most stringent and applies POSIX.1 filename portability testing.
  I.E. characters are limited to [A-Za-z0-9_.-] and max name length = 14 and
  max path length = 255.

  If no path(s) specified then the current directory is assumed.
  

findu8

 $ /usr/share/fslint/fslint/findu8 --help
  find names with invalid UTF8 encoding.
  Usage: findu8 [[-r] [-f] paths(s) ...]

  If no path(s) specified then the current directory is assumed.