1 '\" te
   2 .\" Copyright (c) 2003 Sun Microsystems, Inc.  All Rights Reserved.
   3 .\" Copyright 2016 Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>

   4 .\" Copyright 1989 AT&T
   5 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   6 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   7 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   8 .TH SYSTEM 4 "Jan 25, 2016"
   9 .SH NAME
  10 system \- system configuration information file
  11 .SH DESCRIPTION
  12 .LP
  13 The \fBsystem\fR file is used for customizing the operation of the operating
  14 system kernel. The recommended procedure is to preserve the original
  15 \fBsystem\fR file before modifying it.
  16 .sp
  17 .LP

















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

 343 * by ORing it with 0x40.
 344 set moddebug | 0x40
 345 .fi
 346 .in -2
 347 .sp
 348 
 349 .SH SEE ALSO
 350 .LP
 351 \fBboot\fR(1M), \fBinit\fR(1M), \fBkernel\fR(1M)
 352 .SH WARNINGS
 353 .LP
 354 Use care when modifying the \fBsystem\fR file; it modifies the operation of the
 355 kernel. If you preserved the original \fBsystem\fR file, you can boot using
 356 \fBboot -a\fR, which will ask you to specify the path to the saved file. This
 357 should allow the system to boot correctly. If you cannot locate a \fBsystem\fR
 358 file that will work, you may specify \fB/dev/null\fR. This acts as an empty
 359 \fBsystem\fR file, and the system will attempt to boot using its default
 360 settings.
 361 .SH NOTES
 362 .LP
 363 The \fB/etc/system\fR file is read only once, at boot time.

   1 '\" te
   2 .\" Copyright (c) 2003 Sun Microsystems, Inc.  All Rights Reserved.
   3 .\" Copyright 2016 Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
   4 .\" Copyright 2019 OmniOS Community Edition (OmniOSce) Association.
   5 .\" Copyright 1989 AT&T
   6 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   7 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   8 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   9 .TH SYSTEM 4 "Jan 29, 2019"
  10 .SH NAME
  11 system \- system configuration information file
  12 .SH DESCRIPTION
  13 .LP
  14 The \fBsystem\fR file is used for customizing the operation of the operating
  15 system kernel. The recommended procedure is to preserve the original
  16 \fBsystem\fR file before modifying it.
  17 .sp
  18 .LP
  19 It is not recommended to edit the \fB/etc/system\fR file directly but rather
  20 to deliver configuration fragments into files under \fB/etc/system.d\fR;
  21 files in this directory are combined in alphabetical order and read by the
  22 kernel before \fB/etc/system\fR is processed. Directives in \fB/etc/system\fR
  23 therefore take precedence over any settings delivered in fragment files.
  24 .sp
  25 .LP
  26 The recommended naming schema for the fragment files is to use the name of
  27 the package which is delivering the file with '\fB/\fR' characters replaced
  28 by '\fB:\fR'; file names that start with a dot (\fB.\fR) will be ignored.
  29 .sp
  30 .LP
  31 If \fB/etc/system.d/\fR exists and contains any fragment files,
  32 then the directory must also be writable or it will not be possible to
  33 create or update the system boot archive.
  34 .sp
  35 .LP
  36 The \fBsystem\fR file contains commands which are read by the kernel during
  37 initialization and used to customize the operation of your system. These
  38 commands are useful for modifying the system's treatment of its loadable kernel
  39 modules.
  40 .sp
  41 .LP
  42 The syntax of the \fBsystem\fR file consists of a list of keyword/value pairs
  43 which are recognized by the system as valid commands. Comment lines must begin
  44 with an asterisk (\fB*\fR) or a hash mark (\fB#\fR) and end with a newline
  45 character. All commands are case-insensitive except where noted.
  46 .sp
  47 .LP
  48 Commands that modify the system's operation with respect to loadable kernel
  49 modules require you to specify the module type by listing the module's
  50 namespace. The following namespaces are currently supported on all platforms:
  51 .sp
  52 .ne 2
  53 .na
  54 \fB\fBdrv\fR\fR
  55 .ad

 361 * by ORing it with 0x40.
 362 set moddebug | 0x40
 363 .fi
 364 .in -2
 365 .sp
 366 
 367 .SH SEE ALSO
 368 .LP
 369 \fBboot\fR(1M), \fBinit\fR(1M), \fBkernel\fR(1M)
 370 .SH WARNINGS
 371 .LP
 372 Use care when modifying the \fBsystem\fR file; it modifies the operation of the
 373 kernel. If you preserved the original \fBsystem\fR file, you can boot using
 374 \fBboot -a\fR, which will ask you to specify the path to the saved file. This
 375 should allow the system to boot correctly. If you cannot locate a \fBsystem\fR
 376 file that will work, you may specify \fB/dev/null\fR. This acts as an empty
 377 \fBsystem\fR file, and the system will attempt to boot using its default
 378 settings.
 379 .SH NOTES
 380 .LP
 381 The \fBsystem\fR files are read only once, at boot time.