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
51 .sp
52 .ne 2
53 .na
54 \fB\fBdrv\fR\fR
55 .ad
56 .RS 10n
57 Modules in this namespace are device drivers.
58 .RE
59
60 .sp
61 .ne 2
62 .na
63 \fB\fBexec\fR\fR
64 .ad
65 .RS 10n
66 Modules in this namespace are execution format modules. The following
67 \fBexec\fR modules are currently provided:
68 .sp
69 .ne 2
70 .na
71 \fBOnly on SPARC system:\fR
72 .ad
73 .RS 28n
74 .sp
75 .in +2
76 .nf
77 aoutexec
78 .fi
79 .in -2
80 .sp
81
82 .RE
83
84 .sp
85 .ne 2
86 .na
87 \fBOnly on x86 system:\fR
88 .ad
89 .RS 28n
90 .sp
91 .in +2
92 .nf
93 coffexec
94 .fi
95 .in -2
96 .sp
97
98 .RE
99
100 .sp
101 .ne 2
102 .na
103 \fBOn SPARC and IA systems:\fR
104 .ad
105 .RS 28n
106 .sp
107 .in +2
108 .nf
109 elfexec
110 intpexec
111 javaexec
112 .fi
113 .in -2
114 .sp
115
|
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 2019 Peter Tribble
6 .\" Copyright 1989 AT&T
7 .\" 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.
8 .\" 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.
9 .\" 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]
10 .TH SYSTEM 4 "Apr 20, 2019"
11 .SH NAME
12 system \- system configuration information file
13 .SH DESCRIPTION
14 .LP
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.
18 .sp
19 .LP
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;
22 files in this directory are combined in alphabetical order and read by the
23 kernel before \fB/etc/system\fR is processed. Directives in \fB/etc/system\fR
24 therefore take precedence over any settings delivered in fragment files.
25 .sp
26 .LP
27 The recommended naming schema for the fragment files is to use the name of
28 the package which is delivering the file with '\fB/\fR' characters replaced
29 by '\fB:\fR'; file names that start with a dot (\fB.\fR) will be ignored.
30 .sp
52 .sp
53 .ne 2
54 .na
55 \fB\fBdrv\fR\fR
56 .ad
57 .RS 10n
58 Modules in this namespace are device drivers.
59 .RE
60
61 .sp
62 .ne 2
63 .na
64 \fB\fBexec\fR\fR
65 .ad
66 .RS 10n
67 Modules in this namespace are execution format modules. The following
68 \fBexec\fR modules are currently provided:
69 .sp
70 .ne 2
71 .na
72 \fBOnly on SPARC systems:\fR
73 .ad
74 .RS 28n
75 .sp
76 .in +2
77 .nf
78 aoutexec
79 .fi
80 .in -2
81 .sp
82
83 .RE
84
85 .sp
86 .ne 2
87 .na
88 \fBOn SPARC and IA systems:\fR
89 .ad
90 .RS 28n
91 .sp
92 .in +2
93 .nf
94 elfexec
95 intpexec
96 javaexec
97 .fi
98 .in -2
99 .sp
100
|