kats(1)

     NAME
          kats, kscp, ksmv, ksrm -  K-AShare File Manipulation
          Utilities

     SYNOPSIS
          kats [ -scipSb ] [ -TC type ] [ filename ... ]
          kats -o [ dirname ]
          kscp file1 [ file2 ...  ] target
          ksmv file1 [ file2 ...  ] target
          ksrm file ...

     DESCRIPTION
          These routines let you copy, delete, move and set AppleShare
          attributes for K-AShare files.

          K-AShare stores AppleShare specific information, such as
          file Type and Creator and the resource fork, in several
          utility files. This information will be lost if you use
          cp(1), mv(1) and rm(1), to move K-AShare files around a unix
          filesystem.  If you use kscp, ksmv, and ksrm, the AppleShare
          info will be moved or deleted as necessary.

          Kats is an administrative program used to view and set
          various AppleShare file attributes, including the invisible
          and copy-protected attributes and the Type and Creator
          fields.  Invisible files and directories  will not be
          visible to Appleshare clients. The Macintosh finder will
          refuse to copy copy-protected files.  Directories cannot be
          copy protected.

          When no options are supplied, kats prints out information
          either about the specified files or all files in the current
          directory if no files are specified.

          The attributes are in the .HSancillary file rather than in
          the file itself.  Only the owner of files and root are
          allowed to change attributes.

     OPTIONS
          -s   Set the requested attributes.  This is the default.

          -c   Clear the requested attributes.

          -i   Make the file invisible.

          -b   The file has a bundle.

          -S   The file can be shared.

          -l   The file is locked.

          -o   Check for and delete "orphaned" resource forks from
               dirname (or the current directory if dirname is
               absent).  Orphaned resource forks are .HSResource
               directory entries that have no corresponding data
               files.  Theses files will not appear in K-AShare
               volumes. They can crop up when users use cp, mv and rm
               instead of kscp, ksmv, and ksrm to manipulate K-AShare
               files.  This option has been superceded by the
               dtrebuild(1m) -clean option.

          -p   Copy protect the file.

          -T type
               Change the Macintosh file type.

          -C type
               Change the Macintosh file creator.

     FILES
          */.HSancillary                File for additional file
                                        information needed by
                                        Macintosh.

          */.HSResource/*               Directory for storing the
                                        resource fork of files

     EXAMPLES
          Print information about all files in the current directory:
               kats

          Make the file foo copy-protected:
               kats -ps foo

          Make the file foo a TeachText file:
               kats -T TEXT -C ttxt foo

     SEE ALSO
          K-AShare Administrator's Guide
          ksd(1m)

     CAVEATS
          Once files are typed by K-AShare, the filetype(5) database
          will not be consulted.  If you change the rules for typing a
          particular type of file, it will not change the type of
          already existing files of that type.  The katype(1) program
          can be used to check the validity of your filetype(5)
          database.  Kats shows you the files as K-AShare currently
          has them typed.

     BUGS
          Kats normally should be run in the directory where the
          specified files resides (although if one of the filename
          args has a pathname component, Kats will change to that
          directory before processing).

          If you are not the super-user and you copy or move files
          that you do not own between different directories, the
          permissions of the resulting files may not be set correctly.