SNAT604-5761861-2B ABB 印刷电路板 电源板

SNAT604-5761861-2B ABB 印刷电路板 电源板

NetWare内核模块被称为NetWare可加载模块(NLM)。NLM通过LOAD命令插入NetWare内核，通过UNLOAD命令删除；这模块命令列出了当前加载的内核模块。NLM可以驻留在NetWare服务器上分配的任何有效搜索路径中，并且它们已经。NLM作为文件扩展名。

VxWorks

可以创建一个可下载的内核模块(DKM)类型的项目来生成一个。out”文件，然后可以使用“ld”命令将其加载到内核空间。这个可下载的内核模块可以使用“unld”命令卸载。

Solaris

Solaris有一个可配置的内核模块加载路径，它默认为/平台/平台名称/内核/内核/usr/内核。大多数内核模块位于/内核；那些被认为不是引导系统到init可以启动的点所必需的，通常(但不总是)在/usr/kernel。运行调试内核构建时，系统会主动尝试卸载模块。

二进制兼容性

Linux不提供稳定的应用程序接口或者ABI对于内核模块。这意味着不同内核版本之间的内部结构和功能存在差异，这可能会导致兼容性问题。为了解决这些问题，符号版本控制数据被放在。摩登信息可加载的部分极低频模块。在加载模块之前，可以将该版本信息与正在运行的内核的版本信息进行比较；如果版本不兼容，则不会加载该模块。

其他操作系统，如Solaris,FreeBSD,马科斯，以及Windows操作系统保留内核应用程序接口和ABI相对稳定，从而避免了这个问题。举个例子，FreeBSD针对内核版本6.0编译的内核模块无需在任何其他FreeBSD 6.x版本(如6.4)上重新编译即可运行。但是，它们与其他主要版本不兼容，必须重新编译才能与FreeBSD 7.x一起使用，因为API和ABI兼容性只在一个分支中保持。

SNAT604-5761861-2B ABB 印刷电路板 电源板

NetWare kernel modules are called NetWare Loadable modules (NLM). NLM is inserted into the NetWare kernel using LOAD command and deleted by UNLOAD command. This module command lists the kernel modules currently loaded. NLM can reside in any valid search path assigned on the NetWare server, and they have. NLM as the file extension.

VxWorks

You can create a downloadable kernel module (DKM) type project to generate one. out "file, which can then be loaded into kernel space using the" ld "command. This downloadable kernel module can be uninstalled using the "unld" command.

Solaris

Solaris has a configurable kernel module load path, which defaults to/platform/platform name/kernel/kernel /usr/ kernel. Most kernel modules are located in/kernel; Those that are not considered necessary to boot the system to the point where init can be started are usually (but not always) in /usr/kernel. When you run the debug kernel build, the system actively tries to uninstall the module.

Binary compatibility

Linux does not provide a stable API or ABI for kernel modules. This means there are differences in internal structure and functionality between different kernel versions, which can lead to compatibility issues. To solve these problems, symbolic versioning data is placed. Modern information loadable part of the extremely low frequency module. This version information can be compared with the version information of the running kernel before the module is loaded; If the version is not compatible, the module will not be loaded.

Other operating systems such as Solaris,FreeBSD, Marcos, and Windows operating systems avoid this problem by keeping the kernel application interface and ABI relatively stable. For example, a FreeBSD kernel module compiled for kernel version 6.0 can run without having to be recompiled on any other FreeBSD 6.x version, such as 6.4. However, they are not compatible with other major versions and must be recompiled to work with FreeBSD 7.x, as API and ABI compatibility is only maintained in one branch.