1 SYSTEM(4)               File Formats and Configurations              SYSTEM(4)
   2 
   3 
   4 
   5 NAME
   6        system - system configuration information file
   7 
   8 DESCRIPTION
   9        The system file is used for customizing the operation of the operating
  10        system kernel. The recommended procedure is to preserve the original
  11        system file before modifying it.
  12 
  13 


















  14        The system file contains commands which are read by the kernel during
  15        initialization and used to customize the operation of your system.
  16        These commands are useful for modifying the system's treatment of its
  17        loadable kernel modules.
  18 
  19 
  20        The syntax of the system file consists of a list of keyword/value pairs
  21        which are recognized by the system as valid commands. Comment lines
  22        must begin with an asterisk (*) or a hash mark (#) and end with a
  23        newline character. All commands are case-insensitive except where
  24        noted.
  25 
  26 
  27        Commands that modify the system's operation with respect to loadable
  28        kernel modules require you to specify the module type by listing the
  29        module's namespace. The following namespaces are currently supported on
  30        all platforms:
  31 
  32        drv
  33                  Modules in this namespace are device drivers.

 220          * Demonstrate the cumulative effect of the SET
 221          * bitwise AND/OR operations by further modifying "moddebug"
 222          * by ORing it with 0x40.
 223          set moddebug | 0x40
 224 
 225 
 226 
 227 SEE ALSO
 228        boot(1M), init(1M), kernel(1M)
 229 
 230 WARNINGS
 231        Use care when modifying the system file; it modifies the operation of
 232        the kernel. If you preserved the original system file, you can boot
 233        using boot -a, which will ask you to specify the path to the saved
 234        file. This should allow the system to boot correctly. If you cannot
 235        locate a system file that will work, you may specify /dev/null. This
 236        acts as an empty system file, and the system will attempt to boot using
 237        its default settings.
 238 
 239 NOTES
 240        The /etc/system file is read only once, at boot time.
 241 
 242 
 243 
 244                                January 25, 2016                      SYSTEM(4)

   1 SYSTEM(4)               File Formats and Configurations              SYSTEM(4)
   2 
   3 
   4 
   5 NAME
   6        system - system configuration information file
   7 
   8 DESCRIPTION
   9        The system file is used for customizing the operation of the operating
  10        system kernel. The recommended procedure is to preserve the original
  11        system file before modifying it.
  12 
  13 
  14        It is not recommended to edit the /etc/system file directly but rather
  15        to deliver configuration fragments into files under /etc/system.d;
  16        files in this directory are combined in alphabetical order and read by
  17        the kernel before /etc/system is processed. Directives in /etc/system
  18        therefore take precedence over any settings delivered in fragment
  19        files.
  20 
  21 
  22        The recommended naming schema for the fragment files is to use the name
  23        of the package which is delivering the file with '/' characters
  24        replaced by ':'; file names that start with a dot (.) will be ignored.
  25 
  26 
  27        If /etc/system.d/ exists and contains any fragment files, then the
  28        directory must also be writable or it will not be possible to create or
  29        update the system boot archive.
  30 
  31 
  32        The system file contains commands which are read by the kernel during
  33        initialization and used to customize the operation of your system.
  34        These commands are useful for modifying the system's treatment of its
  35        loadable kernel modules.
  36 
  37 
  38        The syntax of the system file consists of a list of keyword/value pairs
  39        which are recognized by the system as valid commands. Comment lines
  40        must begin with an asterisk (*) or a hash mark (#) and end with a
  41        newline character. All commands are case-insensitive except where
  42        noted.
  43 
  44 
  45        Commands that modify the system's operation with respect to loadable
  46        kernel modules require you to specify the module type by listing the
  47        module's namespace. The following namespaces are currently supported on
  48        all platforms:
  49 
  50        drv
  51                  Modules in this namespace are device drivers.

 238          * Demonstrate the cumulative effect of the SET
 239          * bitwise AND/OR operations by further modifying "moddebug"
 240          * by ORing it with 0x40.
 241          set moddebug | 0x40
 242 
 243 
 244 
 245 SEE ALSO
 246        boot(1M), init(1M), kernel(1M)
 247 
 248 WARNINGS
 249        Use care when modifying the system file; it modifies the operation of
 250        the kernel. If you preserved the original system file, you can boot
 251        using boot -a, which will ask you to specify the path to the saved
 252        file. This should allow the system to boot correctly. If you cannot
 253        locate a system file that will work, you may specify /dev/null. This
 254        acts as an empty system file, and the system will attempt to boot using
 255        its default settings.
 256 
 257 NOTES
 258        The system files are read only once, at boot time.
 259 
 260 
 261 
 262                                January 29, 2019                      SYSTEM(4)