are accepted on some version of Unix or another is: ufs, 4.2,
              4.3, nfs, tmp, mfs, S51K, S52K.  You can use -printf with the %F directive to see the types of your filesystems.

       -gid n File’s numeric group ID is less than, more than or exactly n.

       -group gname
              File belongs to group gname (numeric group ID allowed).

       -ilname pattern
              Like -lname, but the match is case insensitive.  If the -L option or the -follow option is in effect, this test returns false unless the symbolic link is broken.

       -iname pattern
              Like -name, but the match is case insensitive.  For example, the patterns ‘fo*’ and ‘F??’ match the file names ‘Foo’, ‘FOO’, ‘foo’, ‘fOo’, etc.  The pattern ‘*foo*‘ will also match a file called ’.foobar’.

       -inum n
              File has inode number smaller than, greater than or exactly n.  It is normally easier to use the -samefile test instead.

       -ipath pattern
              Like -path.  but the match is case insensitive.

       -iregex pattern
              Like -regex, but the match is case insensitive.

       -iwholename pattern
              See -ipath.  This alternative is less portable than -ipath.

       -links n
              File has less than, more than or exactly n hard links.

       -lname pattern
              File is a symbolic link whose contents match shell pattern pattern.  The metacharacters do not treat ‘/’ or ‘.’ specially.  If the -L option or the -follow option is in effect, this test  returns  false  unless
              the symbolic link is broken.

       -mmin n
              File’s data was last modified less than, more than or exactly n minutes ago.

       -mtime n
              File’s data was last modified less than, more than or exactly n*24 hours ago.  See the comments for -atime to understand how rounding affects the interpretation of file modification times.

       -name pattern
              Base of file name (the path with the leading directories removed) matches shell pattern pattern.  Because the leading directories are removed, the file names considered for a match with -name will never include
              a  slash,  so ‘-name a/b’ will never match anything (you probably need to use -path instead).  A warning is issued if you try to do this, unless the environment variable POSIXLY_CORRECT is set.  The metacharac‐
              ters (‘*’, ‘?’, and ‘[]’) match a ‘.’ at the start of the base name (this is a change in findutils‐4.2.2; see section STANDARDS CONFORMANCE below).  To ignore a directory and the  files  under  it,  use  -prune
              rather  than  checking every file in the tree; see an example in the description of that action.  Braces are not recognised as being special, despite the fact that some shells including Bash imbue braces with a
              special meaning in shell patterns.  The filename matching is performed with the use of the fnmatch(3) library function.  Don’t forget to enclose the pattern in quotes in order to protect it  from  expansion  by
              the shell.

       -newer reference
              Time of the last data modification of the current file is more recent than that of the last data modification of the reference file.  If reference is a symbolic link and the -H option or the -L option is in ef‐
              fect, then the time of the last data modification of the file it points to is always used.

       -newerXY reference
              Succeeds if timestamp X of the file being considered is newer than timestamp Y of the file reference.  The letters X and Y can be any of the following letters:

              a   The access time of the file reference
              B   The birth time of the file reference
              c   The inode status change time of reference
              m   The modification time of the file reference
              t   reference is interpreted directly as a time

              Some  combinations are invalid; for