MODLOAD(8)

NAME
modload - load a kernel module

SYNOPSIS
modload [-dquv] [-A kernel] [-e entry] [-p postinstall] [-o output_file] input_file

DESCRIPTION
The modload utility loads a loadable kernel module into a running system. The input file is an object file (.o file).

The options to modload are as follows:

-d  Debug. Used to debug modload itself.

-q  Be very quiet.

-u  Delete the loaded module (output_file) after loading. If the output file was not specified, this option causes the temporary file to be kept rather than deleted.

-v  Print comments about the loading process.

-A kernel
    Specify the file that is passed to the linker to resolve module references to external symbols. The symbol file must be for the currently running kernel or the module is likely to crash the system.

-e entry
    Specify the module entry point. This is passed by modload to ld(1) when the module is linked. The default module entry point name is the module name with `_mod' appended.

-p postinstall
    Specify the name of a shell script or program that will be executed if the module is successfully loaded. It is always passed the module id (in decimal) and module type (in hexadecimal) as the first two arguments. For loadable drivers, the third argument is the block or character major device number. For a loadable system call, the third argument is the system call number.

-o output_file
    Specify the name of the output file that is produced by the linker. If this option is not specified, a file in the /tmp directory is used with the name generated from the module name with a `.out' extension.

FILES
/kernel
    default file passed to the linker to resolve external references in the module
/usr/include/sys/lkm.h
    file containing definitions of module types

DIAGNOSTICS
The modload utility exits with a status of 0 on success and with a nonzero status if an error occurs.

SEE ALSO
ld(1), lkm(4), modstat(8), modunload(8)

HISTORY
The modload command was designed to be similar in functionality to the corresponding command in SunOS 4.1.3.

AUTHOR
Terrence R. Lambert, terry@cs.weber.edu

BUGS
The loadable device driver framework can only reserve either a character or block device entry, not both.