modpath(2) [hpux man page]
modpath(2) System Calls Manual modpath(2) NAME
modpath - change global search path for dynamically loadable kernel modules SYNOPSIS
DESCRIPTION
allows processes with appropriate privilege to modify the global search path used to locate object files for dynamically loadable kernel modules. The search path modifications take effect immediately and affect all subsequent loads for all users on the system. pathname may be either a colon-separated list of absolute path names or NULL. If the former, these path names represent directories which should be searched for all autoloads of loadable kernel modules and for demand loads (see modload(2)) where the module is given by a simple file name. This list of directories will be prepended to the existing list of directories and so will be searched before any directories given in previous calls to and before the default location which is always searched last. The directories do not have to exist on the sys- tem at the time is called, or when a load actually takes place. If pathname is equal to NULL, the global search path is set back to its initial default value, Notes is currently implemented as a macro. Module search path is not persistent across boots. Security Restrictions is restricted to superuser processes or privileged processes. A privileged process requires the privilege to execute the system call. See privileges(5) for more information about the privilege. RETURN VALUE
On success, returns 0, otherwise it returns -1 and sets to indicate the error. ERRORS
fails if one or more of the following are true: The list of directories specified by pathname is malformed. The Dynamically Loadable Kernel Module feature is not initialized. pathname is more than characters long. The caller is not a superuser process or a privileged process. SEE ALSO
kcmodule(1M), modload(2), privileges(5). modpath(2)
Check Out this Related Man Page
modload(1M) System Administration Commands modload(1M) NAME
modload - load a kernel module SYNOPSIS
modload [-p] [-e exec_file] filename DESCRIPTION
The modload command 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 slash (/), 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. For example, the following command looks for ./drv/foo: example# modload drv/foo The following command looks for /kernel/drv/foo and then /usr/kernel/drv/foo: example# modload -p drv/foo OPTIONS
The following options are supported: -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) -p Use the kernel's internal modpath variable as the search path for the module. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
ld(1), add_drv(1M), kernel(1M), modinfo(1M), modunload(1M), system(4), attributes(5), modldrv(9S), modlinkage(9S), modlstrmod(9S), mod- ule_info(9S) Writing Device Drivers NOTES
Use add_drv(1M) to add device drivers, not modload. See Writing Device Drivers for procedures on adding device drivers. SunOS 5.10 1 Dec 1993 modload(1M)