Software Distributor Administration Guide (March 2009)

10.4.2.4.11.1 Default Permission Specifications
By default, a destination file will inherit the mode, owner, and group of the source file.
You can use the file_permissions keyword to set a default permission mask, owner,
and group for all the files being packaged into the fileset:
file_permissions [-m mode| -u umask] [-o [owner[,]] [uid]] [-g [group[,]][gid]][-t
type]
file_permissions
This keyword applies only to the fileset in which it is
defined. You can specify multiple file_permissions;
later definitions replace previous definitions.
-m mode
This option defines a default (octal) mode for all files.
-u umask
Instead of specifying an octal mode as the default, you
can specify an octal umask (1) value that gets “subtracted”
from an existing source file’s mode to generate the mode
of the destination file.
By specifying a umask, you can set a default mode for
executable files, non-executable files, and directories. (A
specific mode can be set for any file using -m.)
-o [owner[,]][uid]
This option defines the destination file’s owner name
and/or or uid. See the discussion of the -o option in
“Explicit File Specification ” (page 244) for more
information.
-g [group[,]][gid]
This option defines the destination file’s group name
and/or or gid. See the discussion of the -g option in
“Explicit File Specification ” (page 244) for more
information.
-t type
Defines files that need not exist before packaging.
The following examples illustrate the use of the file_permission keyword.
• Set a read only 444 mode for all file objects (requires override for every executable
file and directory):
file_permissions -m 444
• Set a read mode for non-executable files, and a read/execute mode for executable
files and directories:
file_permissions -u 222
• Set the same mode defaults, plus an owner and group:
file_permissions -u 222 -o bin -g bin
• Set the same mode defaults, plus a uid and gid:
file_permissions -u 222 -o 2 -g 2
10.4 Creating a Product Specification File (PSF) 243