38 The syntax of the system file consists of a list of keyword/value pairs
39 which are recognized by the system as valid commands. Comment lines
40 must begin with an asterisk (*) or a hash mark (#) and end with a
41 newline character. All commands are case-insensitive except where
42 noted.
43
44
45 Commands that modify the system's operation with respect to loadable
46 kernel modules require you to specify the module type by listing the
47 module's namespace. The following namespaces are currently supported on
48 all platforms:
49
50 drv
51 Modules in this namespace are device drivers.
52
53
54 exec
55 Modules in this namespace are execution format modules. The
56 following exec modules are currently provided:
57
58 Only on SPARC system:
59
60 aoutexec
61
62
63
64
65 Only on x86 system:
66
67 coffexec
68
69
70
71
72 On SPARC and IA systems:
73
74 elfexec
75 intpexec
76 javaexec
77
78
79
80
81
82 firmware
83 Raw firmware images in subdirectories, one for each device
84 driver module using firmload(9F).
85
86
87 fs
88 These modules are filesystems.
89
90
91 sched
242
243
244
245 SEE ALSO
246 boot(1M), init(1M), kernel(1M)
247
248 WARNINGS
249 Use care when modifying the system file; it modifies the operation of
250 the kernel. If you preserved the original system file, you can boot
251 using boot -a, which will ask you to specify the path to the saved
252 file. This should allow the system to boot correctly. If you cannot
253 locate a system file that will work, you may specify /dev/null. This
254 acts as an empty system file, and the system will attempt to boot using
255 its default settings.
256
257 NOTES
258 The system files are read only once, at boot time.
259
260
261
262 January 29, 2019 SYSTEM(4)
|
38 The syntax of the system file consists of a list of keyword/value pairs
39 which are recognized by the system as valid commands. Comment lines
40 must begin with an asterisk (*) or a hash mark (#) and end with a
41 newline character. All commands are case-insensitive except where
42 noted.
43
44
45 Commands that modify the system's operation with respect to loadable
46 kernel modules require you to specify the module type by listing the
47 module's namespace. The following namespaces are currently supported on
48 all platforms:
49
50 drv
51 Modules in this namespace are device drivers.
52
53
54 exec
55 Modules in this namespace are execution format modules. The
56 following exec modules are currently provided:
57
58 Only on SPARC systems:
59
60 aoutexec
61
62
63
64
65 On SPARC and IA systems:
66
67 elfexec
68 intpexec
69 javaexec
70
71
72
73
74
75 firmware
76 Raw firmware images in subdirectories, one for each device
77 driver module using firmload(9F).
78
79
80 fs
81 These modules are filesystems.
82
83
84 sched
235
236
237
238 SEE ALSO
239 boot(1M), init(1M), kernel(1M)
240
241 WARNINGS
242 Use care when modifying the system file; it modifies the operation of
243 the kernel. If you preserved the original system file, you can boot
244 using boot -a, which will ask you to specify the path to the saved
245 file. This should allow the system to boot correctly. If you cannot
246 locate a system file that will work, you may specify /dev/null. This
247 acts as an empty system file, and the system will attempt to boot using
248 its default settings.
249
250 NOTES
251 The system files are read only once, at boot time.
252
253
254
255 April 20, 2019 SYSTEM(4)
|