[Go to CFHT Home Page] Man Pages
Back to Software Index  BORDER=0Manpage Top Level
    modload(1M) manual page Table of Contents

Name

modload - load a kernel module

Synopsis

modload [ -p ] [ -e exec_file ] filename

Availability

SUNWcsu

Description

modload loads the loadable module filename into the running system. filename is an object file produced by ld -r. If filename is an absolute pathname then the file specified by that absolute path is loaded. If filename does not begin with a ’/’ then the path to load filename is relative to the current directory unless the -p option is specified. The kernel’s modpath variable can be set using the /etc/system file. The default value of the kernel’s modpath variable is set to the path where the operating system was loaded. Typically this is /kernel /usr/kernel. Hence if you type:

example# modload drv/foo

Then the kernel will look for ./drv/foo.

If you type:

example# modload -p drv/foo

Then the kernel will look for /kernel/drv/foo and then /usr/kernel/drv/foo.

Options

-p
Use the kernel’s internal modpath variable as the search path for the module.
-e exec_file
Specify the name of a shell script or executable image file that is executed after the module is successfully loaded. The first argument passed is the module ID (in decimal). The other argument is module specific. The module specific information is: the block and character major numbers for drivers, the system call number for system calls, or, for other module types, the index into the appropriate kernel table. See modinfo(1M) .

See Also

ld(1) , add_drv(1M) , kernel(1M) , modinfo(1M) , modunload(1M) , system(4) , modldrv(9S) , modlinkage(9S) , modlstrmod(9S) , module_info(9S)


Notes

Use add_drv(1M) to add device drivers, not modload. See for procedures on adding device drivers.


Table of Contents