kernel - UNIX system executable file containing basic operating system services
kernel-name [-asrvx] [-m smf_options] [-i altinit]
The operating system image, or kernel, is the collection of software comprising the image files (unix and genunix) and the modules loaded at any instant in time. The system will not function without a kernel to control it.
The kernel is loaded by the boot(8) command in a machine-specific way. The kernel may be loaded from disk, CD-ROM, or DVD (diskfull boot) or over the network (diskless boot). In either case, the directories under /platform and /kernel must be readable and must contain executable code which is able to perform the required kernel service. If the –a flag is given, the user is able to supply different pathnames for the default locations of the kernel and modules. See boot(8) for more information on loading a specific kernel.
The moddir variable contains a list of module directories separated by whitespace. moddir can be set in the /etc/system file. The minimal default is:
/platform/platform-name/kernel /kernel /usr/kernel
This default can be supplemented by a specific platform. It is common for many SPARC systems to override the default path with:
The kernel configuration can be controlled using the /etc/system file (see system(5)).
genunix is the platform-independent component of the base kernel.
The following options are supported:
Asks the user for configuration information, such as where to find the system file, where to mount root, and even override the name of the kernel itself. Default responses will be contained in square brackets ([ ]), and the user may simply enter RETURN to use the default response (note that RETURN is labeled ENTER on some keyboards). To help repair a damaged /etc/system file, enter /dev/null at the prompt that asks for the pathname of the system configuration file. See system(5).
Select an alternative executable to be the primordial process. altinit must be a valid path to an executable. The default primordial process is init(8).
The smf_options include two categories of options to control booting behavior of the service management facility: recovery options and messages options.
Message options determine the type and amount of messages that smf(7) displays during boot. Service options determine the services which are used to boot the system.
Prints standard per-service output and all svc.startd messages to log.
Boot with some SMF services temporarily disabled, as indicated by milestone. milestone can be “none”, “single-user”, “multi-user”, “multi-user-server”, or “all”. See the milestone subcommand of svcadm(8).
Prints standard per-service output and error messages requiring administrative intervention.
Prints standard per-service output with more informational messages.
Reconfiguration boot. The system will probe all attached hardware devices and configure the logical namespace in /dev. See add_drv(8) and rem_drv(8) for additional information about maintaining device drivers.
Boots only to init level 's'. See init(8).
Boots with verbose messages enabled. If this flag is not given, the messages are still printed, but the output is directed to the system logfile. See syslogd(8).
Does not boot in clustered mode. This option only has an effect when a version of Oracle Solaris Cluster software that supports this option has been installed.
See boot(8) for examples and instructions on how to boot.
Contains kernel components common to all platforms within a particular instruction set that are needed for booting the system.
The platform-specific kernel components.
The kernel components specific to this hardware class.
Contains kernel components common to all platforms within a particular instruction set.
The directories in this section can potentially contain the following subdirectories:
Loadable device drivers
The modules that execute programs stored in various file formats.
File system modules
Miscellaneous system-related modules
Operating system schedulers
System V STREAMS loadable modules
Loadable system calls
Processor specific modules
Time-Of-Day hardware interface modules
As only 64-bit SPARC platforms are supported, all SPARC executable modules are contained within sparcv9 subdirectories in the directories listed above.
x86 hardware support
As only 64-bit x86 platforms are supported, all x86 executable modules are contained within amd64 subdirectories in the directories listed above.
See attributes(7) for descriptions of the following attributes:
The kernel gives various warnings and error messages. If the kernel detects an unrecoverable fault, it will panic or halt.
Reconfiguration boot will, by design, not remove /dev entries for some classes of devices that have been physically removed from the system.