LOADER.4TH(7) | Standards, Environments, and Macros | LOADER.4TH(7) |
loader.4th
—
loader.conf processing tools
The file that goes by the name of
loader.4th
is a set of commands designed to
manipulate loader.conf(5) files.
The default /boot/loader.rc includes
loader.4th
and uses one of its commands to
automatically read and process the standard
loader.conf(5) files. Other
commands exists to help the user specify alternate configurations.
The commands of loader.4th
by themselves
are not enough for most uses. Please refer to the examples below for the
most common situations, and to
loader(7) for additional commands.
Before using any of the commands provided in
loader.4th
, it must be included through the
command:
include loader.4th
This line is present in the default /boot/loader.rc file, so it is not needed (and should not be re-issued) in a normal setup.
The commands provided by it are:
boot
boot
kernelname [...
]boot
directory [...
]boot
-flag
...
Depending on the arguments passed, it can override boot flags and either the kernel name or the search path for kernel and modules.
boot-conf
boot-conf
kernelname [...
]boot-conf
directory [...
]boot-conf
-flag
...
boot
described above, but instead of
booting immediately, uses autoboot
, so it can be
stopped.
start
boot
or
autoboot
commands or simply exit (provided
autoboot_delay is not set to NO) to boot the system.
start
is the command used in the default
/boot/loader.rc file (see
loader(7)).
initialize
start
first. Like start
,
it reads /boot/defaults/loader.conf and all other
loader.conf(5) files specified
in it (but does not load kernel or modules). Returns a flag on the stack
to indicate if any configuration files were successfully loaded.
read-conf
filenameenable-module
moduledisable-module
moduletoggle-module
moduleshow-module
moduleshow-module-options
retry
ignore
try-include
file [file ...]Standard /boot/loader.rc:
include /boot/forth/loader.4th start
Read an additional configuration file and then proceed to boot:
unload read-conf /boot/special.conf boot-conf
April 22, 2017 | OmniOS |