BOM(5)                  COMMAND REFERENCE                  BOM(5)



NAME
     bom - Bill of Materials specification file format for use
     with comply

DESCRIPTION
     For each file to be checked for compliance the comply(8)
     specification file contains the following information:

          pathname (full or relative to comply(8) invocation)
          owner
          group
          mode
          size
          hard link count
          rcsid number
          checksum
          symlink target

     This is an ASCII file. Each field within each specification
     entry is separated from the next field by a tab.  Each
     specification is separated from the next specification by a
     new-line.  Any line beginning with a % will be considered a
     comment.  If the first line in the file begins with a
     comment, that comment will be used as a verbose description
     of the comply specification file when comply(8) runs.  All
     blank lines are ignored.

     If any of the above described fields are empty (bracketed by
     tabs), then comply will not bother to check compliance to
     those fields; this is true for all fields but pathname,
     mode, and symbolic link target when the file type is
     symbolic link fields.

FIELDS
     pathname    This can be an absolute path (i.e. starts with
                 /), or it can be a relative path from the
                 current working directory of the comply(8)
                 invocation.

     owner       Login name of the owner of the file/directory.

     group       Symbolic name of the group owner of the
                 file/directory.

     mode        This field contains both the file type and the
                 file mode.  The format for this is as in ls(1).
                 The first character specifies the file type.
                 Directories, block special, character special,
                 symbolically linked, and regular files are
                 denoted by d, b, c, l, and -, respectively.  The
                 remaining nine characters specify the mode.  The
                 read (r), write (w), or execute (x) permissions



Printed 3/13/89                                                 1

BOM(5)                  COMMAND REFERENCE                  BOM(5)



                 are in the order for owner, group, and others.
                 Instead of x for the owner (or group), s
                 designates a setuid (setgid) program.
                 Similarly, t instead of x in the other mode
                 designates a program with the sticky bit on.

     size        The size in bytes on the disk, this does not
                 represent the size of the file/program in a
                 running state in core.  Or, if the file is a
                 device, this field should be the major/minor
                 device numbers - comma or space separated.

     hard link count
                 Number of hard links to this file.

     rcsid number
                 This is the RCS revision number associated with
                 the file (e.g. 1.35).

     checksum    Checksum of the file as provided by the sum(1)
                 command.

     symlink target
                 This is the target file/directory name if this
                 file is a symbolic link.  This has the same form
                 as pathname.

EXAMPLES
     An example of a bom file follows where the at symbol ( @ )
     is used to signify a tab.

          /etc/catman@sys@sys@-rwxr-xr-x@16384@1@1.4@65389@
          /etc/chown@root@sys@-rwxr-xr-x@10360@1@1.17@31625@
          /bin/ll@sys@sys@lrwxr-xr-x@16384@1@3.2@52346@/bin/ls

SEE ALSO
     comply(8), ident(1rcs), ls(1), rcs(1rcs), and sum(1).


















Printed 3/13/89                                                 2

%%index%%
na:216,126;
de:342,2583;3213,1354;
ex:4567,400;
se:4967,213;
%%index%%000000000094