Print this page
9696 add /etc/system.d support
Portions contributed by: Andy Fiddaman <andy@omniosce.org>
Reviewed by: Hans Rosenfeld <hans.rosenfeld@joyent.com>
Reviewed by: Peter Tribble <peter.tribble@gmail.com>
Reviewed by: C Fraire <cfraire@me.com>
Reviewed by: Toomas Soome <tsoome@me.com>

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man4/system.4.man.txt
          +++ new/usr/src/man/man4/system.4.man.txt
↓ open down ↓ 3 lines elided ↑ open up ↑
   4    4  
   5    5  NAME
   6    6         system - system configuration information file
   7    7  
   8    8  DESCRIPTION
   9    9         The system file is used for customizing the operation of the operating
  10   10         system kernel. The recommended procedure is to preserve the original
  11   11         system file before modifying it.
  12   12  
  13   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 +
  14   32         The system file contains commands which are read by the kernel during
  15   33         initialization and used to customize the operation of your system.
  16   34         These commands are useful for modifying the system's treatment of its
  17   35         loadable kernel modules.
  18   36  
  19   37  
  20   38         The syntax of the system file consists of a list of keyword/value pairs
  21   39         which are recognized by the system as valid commands. Comment lines
  22   40         must begin with an asterisk (*) or a hash mark (#) and end with a
  23   41         newline character. All commands are case-insensitive except where
↓ open down ↓ 206 lines elided ↑ open up ↑
 230  248  WARNINGS
 231  249         Use care when modifying the system file; it modifies the operation of
 232  250         the kernel. If you preserved the original system file, you can boot
 233  251         using boot -a, which will ask you to specify the path to the saved
 234  252         file. This should allow the system to boot correctly. If you cannot
 235  253         locate a system file that will work, you may specify /dev/null. This
 236  254         acts as an empty system file, and the system will attempt to boot using
 237  255         its default settings.
 238  256  
 239  257  NOTES
 240      -       The /etc/system file is read only once, at boot time.
      258 +       The system files are read only once, at boot time.
 241  259  
 242  260  
 243  261  
 244      -                               January 25, 2016                      SYSTEM(4)
      262 +                               January 29, 2019                      SYSTEM(4)
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX