Lines Matching +full:system +full:- +full:on +full:- +full:module

3 .\" Copyright 2016 Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
11 .TH SYSTEM 5 "June 30, 2022"
13 system \- system configuration information file
15 The \fBsystem\fR file is used for customizing the operation of the operating
16 system kernel. The recommended procedure is to preserve the original
17 \fBsystem\fR file before modifying it.
20 It is not recommended to edit the \fB/etc/system\fR file directly but rather
21 to deliver configuration fragments into files under \fB/etc/system.d\fR;
23 kernel before \fB/etc/system\fR is processed. Directives in \fB/etc/system\fR
32 If \fB/etc/system.d/\fR exists and contains any fragment files,
34 create or update the system boot archive.
37 The \fBsystem\fR file contains commands which are read by the kernel during
38 initialization and used to customize the operation of your system. These
39 commands are useful for modifying the system's treatment of its loadable kernel
43 The syntax of the \fBsystem\fR file consists of a list of keyword/value pairs
44 which are recognized by the system as valid commands. Comment lines must begin
46 character. All commands are case-insensitive except where noted.
49 Commands that modify the system's operation with respect to loadable kernel
50 modules require you to specify the module type by listing the module's
51 namespace. The following namespaces are currently supported on all platforms:
58 These modules provide rules and actions for device auto-configuration.
94 module using \fBfirmload\fR(9F).
130 These modules implement loadable system-call modules.
153 Do not allow the listed loadable kernel module to be loaded. \fBexclude\fR
155 combining every \fBexclude\fR entry in the \fBsystem\fR file.
165 Include the listed loadable kernel module. This is the system's default, so
166 using \fBinclude\fR does not modify the system's operation. \fBinclude\fR
177 Force this kernel module to be loaded during kernel initialization. The default
178 action is to automatically load the kernel module when its services are first
206 \fB\fBmoddir:\fR <\fIfirst module path\fR>[[{:, }<\fIsecond ...\fR>]...]\fR
218 \fB\fBset\fR [\fI<module>\fR:]\fI<symbol>\fR {=, |, &} [~][-]\fI<value>\fR\fR
223 module to a new value. This command is used to change kernel and module
224 parameters and thus modify the operation of your system. Assignment operations
230 and negation. Variables in a specific loadable module can be targeted for
231 modification by specifying the variable name prefixed with the kernel module
254 \fBExample 1 \fRA sample \fBsystem\fR file.
256 The following is a sample \fBsystem\fR file.
261 * Force the ELF exec kernel module to be loaded during kernel
269 * SCSI target 3 on the esp host adapter in slot 0 (on board)
271 * Adapter unit-address 3,0 at sbus unit-address 0,800000.
279 * Note that you can delimit your module pathnames using
287 * Turn on debugging messages in the modules mydriver. This is useful
307 Use care when modifying the \fBsystem\fR file; it modifies the operation of the
308 kernel. If you preserved the original \fBsystem\fR file, you can boot using
309 \fBboot -a\fR, which will ask you to specify the path to the saved file. This
310 should allow the system to boot correctly. If you cannot locate a \fBsystem\fR
312 \fBsystem\fR file, and the system will attempt to boot using its default
315 The \fBsystem\fR files are read only once, at boot time.