Print this page
10832 system.4 refers to coffexec
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man4/system.4.man.txt
+++ new/usr/src/man/man4/system.4.man.txt
1 1 SYSTEM(4) File Formats and Configurations SYSTEM(4)
2 2
3 3
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 14 It is not recommended to edit the /etc/system file directly but rather
15 15 to deliver configuration fragments into files under /etc/system.d;
16 16 files in this directory are combined in alphabetical order and read by
17 17 the kernel before /etc/system is processed. Directives in /etc/system
18 18 therefore take precedence over any settings delivered in fragment
19 19 files.
20 20
21 21
22 22 The recommended naming schema for the fragment files is to use the name
23 23 of the package which is delivering the file with '/' characters
24 24 replaced by ':'; file names that start with a dot (.) will be ignored.
25 25
26 26
27 27 If /etc/system.d/ exists and contains any fragment files, then the
28 28 directory must also be writable or it will not be possible to create or
29 29 update the system boot archive.
30 30
31 31
32 32 The system file contains commands which are read by the kernel during
33 33 initialization and used to customize the operation of your system.
34 34 These commands are useful for modifying the system's treatment of its
35 35 loadable kernel modules.
36 36
37 37
38 38 The syntax of the system file consists of a list of keyword/value pairs
39 39 which are recognized by the system as valid commands. Comment lines
40 40 must begin with an asterisk (*) or a hash mark (#) and end with a
41 41 newline character. All commands are case-insensitive except where
42 42 noted.
43 43
44 44
45 45 Commands that modify the system's operation with respect to loadable
46 46 kernel modules require you to specify the module type by listing the
47 47 module's namespace. The following namespaces are currently supported on
|
↓ open down ↓ |
47 lines elided |
↑ open up ↑ |
48 48 all platforms:
49 49
50 50 drv
51 51 Modules in this namespace are device drivers.
52 52
53 53
54 54 exec
55 55 Modules in this namespace are execution format modules. The
56 56 following exec modules are currently provided:
57 57
58 - Only on SPARC system:
58 + Only on SPARC systems:
59 59
60 60 aoutexec
61 61
62 62
63 63
64 64
65 - Only on x86 system:
66 -
67 - coffexec
68 -
69 -
70 -
71 -
72 65 On SPARC and IA systems:
73 66
74 67 elfexec
75 68 intpexec
76 69 javaexec
77 70
78 71
79 72
80 73
81 74
82 75 firmware
83 76 Raw firmware images in subdirectories, one for each device
84 77 driver module using firmload(9F).
85 78
86 79
87 80 fs
88 81 These modules are filesystems.
89 82
90 83
91 84 sched
92 85 These modules implement a process scheduling algorithm.
93 86
94 87
95 88 strmod
96 89 These modules are STREAMS modules.
97 90
98 91
99 92 sys
100 93 These modules implement loadable system-call modules.
101 94
102 95
103 96 misc
104 97 These modules do not fit into any of the above categories, so
105 98 are considered "miscellaneous" modules.
106 99
107 100
108 101
109 102 SPARC only:
110 103
111 104 dacf
112 105 These modules provide rules and actions for device auto-
113 106 configuration.
114 107
115 108
116 109 tod
117 110 These modules provide support for the time of day hardware.
118 111
119 112
120 113 cpu
121 114 These modules provide CPU-specific kernel routines.
122 115
123 116
124 117
125 118 A description of each of the supported commands follows:
126 119
127 120 exclude: <namespace>/<modulename>
128 121
129 122 Do not allow the listed loadable kernel module to be loaded.
130 123 exclude commands are cumulative; the list of modules to exclude is
131 124 created by combining every exclude entry in the system file.
132 125
133 126
134 127 include: <namespace>/<modulename>
135 128
136 129 Include the listed loadable kernel module. This is the system's
137 130 default, so using include does not modify the system's operation.
138 131 include commands are cumulative.
139 132
140 133
141 134 forceload: <namespace>/<modulename>
142 135
143 136 Force this kernel module to be loaded during kernel initialization.
144 137 The default action is to automatically load the kernel module when
145 138 its services are first accessed. forceload commands are cumulative.
146 139
147 140
148 141 rootdev: <device name>
149 142
150 143 Set the root device to the listed value instead of using the
151 144 default root device as supplied by the boot program.
152 145
153 146
154 147 rootfs: <root filesystem type>
155 148
156 149 Set the root filesystem type to the listed value.
157 150
158 151
159 152 moddir: <first module path>[[{:, }<second ...>]...]
160 153
161 154 Set the search path for loadable kernel modules. This command
162 155 operates very much like the PATH shell variable. Multiple
163 156 directories to search can be listed together, delimited either by
164 157 blank spaces or colons.
165 158
166 159
167 160 set [<module>:]<symbol> {=, |, &} [~][-]<value>
168 161
169 162 Set an integer or character pointer in the kernel or in the
170 163 selected kernel module to a new value. This command is used to
171 164 change kernel and module parameters and thus modify the operation
172 165 of your system. Assignment operations are not cumulative, whereas
173 166 bitwise AND and OR operations are cumulative.
174 167
175 168 Operations that are supported for modifying integer variables are:
176 169 simple assignment, inclusive bitwise OR, bitwise AND, one's
177 170 complement, and negation. Variables in a specific loadable module
178 171 can be targeted for modification by specifying the variable name
179 172 prefixed with the kernel module name and a colon (:) separator.
180 173 Values can be specified as hexadecimal (0x10), Octal (046), or
181 174 Decimal (5).
182 175
183 176 The only operation supported for modifying character pointers is
184 177 simple assignment. Static string data such as character arrays
185 178 cannot be modified using the set command. Use care and ensure that
186 179 the variable you are modifying is in fact a character pointer. The
187 180 set command is very powerful, and will likely cause problems if
188 181 used carelessly. The following escape sequences are supported
189 182 within the quoted string:
190 183
191 184 \n (newline)
192 185 \t (tab)
193 186 \b (backspace)
194 187
195 188
196 189
197 190
198 191 EXAMPLES
199 192 Example 1 A sample system file.
200 193
201 194
202 195 The following is a sample system file.
203 196
204 197
205 198 * Force the ELF exec kernel module to be loaded during kernel
206 199 * initialization. Execution type modules are in the exec namespace.
207 200 forceload: exec/elfexec
208 201 * Change the root device to /sbus@1,f8000000/esp@0,800000/sd@3,0:a.
209 202 * You can derive root device names from /devices.
210 203 * Root device names must be the fully expanded Open Boot Prom
211 204 * device name. This command is platform and configuration specific.
212 205 * This example uses the first partition (a) of the SCSI disk at
213 206 * SCSI target 3 on the esp host adapter in slot 0 (on board)
214 207 * of the SBus of the machine.
215 208 * Adapter unit-address 3,0 at sbus unit-address 0,800000.
216 209 rootdev: /sbus@1,f8000000/esp@0,800000/sd@3,0:a
217 210 * Set the filesystem type of the root to ufs. Note that
218 211 * the equal sign can be used instead of the colon.
219 212 rootfs:ufs
220 213 * Set the search path for kernel modules to look first in
221 214 * /usr/phil/mod_test for modules, then in /kernel/modules (the
222 215 * default) if not found. Useful for testing new modules.
223 216 * Note that you can delimit your module pathnames using
224 217 * colons instead of spaces: moddir:/newmodules:/kernel/modules
225 218 moddir:/usr/phil/mod_test /kernel/modules.
226 219 * Set the configuration option {_POSIX_CHOWN_RESTRICTED} :
227 220 * This configuration option is enabled by default.
228 221 set rstchown = 1
229 222 * Disable the configuration option {_POSIX_CHOWN_RESTRICTED} :
230 223 set rstchown = 0
231 224 * Turn on debugging messages in the modules mydriver. This is useful
232 225 * during driver development.
233 226 set mydriver:debug = 1
234 227 * Bitwise AND the kernel variable "moddebug" with the
235 228 * one's complement of the hex value 0x880, and set
236 229 * "moddebug" to this new value.
237 230 set moddebug & ~0x880
238 231 * Demonstrate the cumulative effect of the SET
239 232 * bitwise AND/OR operations by further modifying "moddebug"
240 233 * by ORing it with 0x40.
241 234 set moddebug | 0x40
242 235
243 236
244 237
245 238 SEE ALSO
246 239 boot(1M), init(1M), kernel(1M)
247 240
248 241 WARNINGS
249 242 Use care when modifying the system file; it modifies the operation of
250 243 the kernel. If you preserved the original system file, you can boot
251 244 using boot -a, which will ask you to specify the path to the saved
|
↓ open down ↓ |
170 lines elided |
↑ open up ↑ |
252 245 file. This should allow the system to boot correctly. If you cannot
253 246 locate a system file that will work, you may specify /dev/null. This
254 247 acts as an empty system file, and the system will attempt to boot using
255 248 its default settings.
256 249
257 250 NOTES
258 251 The system files are read only once, at boot time.
259 252
260 253
261 254
262 - January 29, 2019 SYSTEM(4)
255 + April 20, 2019 SYSTEM(4)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX