1 .\" Copyright (c) 1993 Christopher G. Demetriou
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. The name of the author may not be used to endorse or promote products
13 .\" derived from this software without specific prior written permission
15 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
16 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
17 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
18 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
19 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
20 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
21 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
22 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
23 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
24 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
33 .Nd dynamic kernel linker facility
35 The LKM (Loadable Kernel Modules) facility has been deprecated in
37 and above in favor of the
40 This interface, like its
41 predecessor, allows the system administrator to dynamically add and remove
42 functionality from a running system.
43 This ability also helps software
44 developers to develop new parts of the kernel without constantly rebooting
45 to test their changes.
47 Various types of modules can be loaded into the system.
48 There are several defined module types, listed below, which can
49 be added to the system in a predefined way.
51 is a generic type, for which the module itself handles loading and
56 system makes extensive use of loadable kernel modules, and provides loadable
57 versions of most file systems, the
59 client and server, all the screen-savers, and the
65 modules are placed by default in the
67 directory along with their matching kernel.
71 interface is used through the
80 program can load either
82 or ELF formatted loadable modules.
85 program unloads any given loaded module, if no other module is dependent
86 upon the given module.
89 program is used to check the status of the modules currently loaded into the
92 Kernel modules may only be loaded or unloaded if the system security level
97 .It Em "Device Driver modules"
98 New block and character device
99 drivers may be loaded into the system with
101 Device nodes for the loaded drivers are automatically created when a
102 module is loaded and destroyed when it is unloaded by
104 You can specify userland programs that will run when new devices
105 become available as a result of loading modules, or existing devices
106 go away when modules are unloaded, by configuring
110 .Bl -tag -width /usr/include/sys/module.h -compact
112 directory containing module binaries built for the kernel also
113 residing in the directory.
114 .It Pa /usr/include/sys/module.h
115 file containing definitions required to compile a
118 .It Pa /usr/share/examples/kld
119 example source code implementing a sample kld module
139 and was designed as a replacement for the
141 facility, which was similar in functionality to the loadable kernel modules
148 facility was originally implemented by
149 .An Doug Rabson Aq dfr@FreeBSD.org .
151 If a module B, is dependent on another module A, but is not compiled with
152 module A as a dependency, then
154 fails to load module B, even if module A is already present in the system.
156 If multiple modules are dependent on module A, and are compiled with module
157 A as a dependency, then
159 loads an instance of module A when any of the modules are loaded.
161 If a custom entry point is used for a module, and the module is compiled as
166 fails to execute the entry point.
169 returns the cryptic message
170 .Sq Li "ENOEXEC (Exec format error)"
171 for any error encountered while loading a module.
173 When system internal interfaces change, old modules often cannot
174 detect this, and such modules when loaded will often cause crashes or