Talk:Loadable kernel module

This article contains mostly general info about LKM

This article contains mostly general info about LKM and i don't think it needs to be Linux-specific. Linux is OK as an example, though. ~~helix84 15:32, 11 January 2006 (UTC)[reply]

So:

add more Technical details on this page
use the data inside this article on a generalistic module page

00 tux 01:17, 29 April 2006 (UTC)[reply]

KLM or LKM ?

I have heard of LKMs referred-to as KLMs (Kernel Loadable Modules). Is this common usage? Should the KLM initialism also be captured here? ppblais 13:23, 27 April 2006 (UTC)

explain the "loadable"! how is a module loaded an unloaded

I tagged the article as needing cleanup, for several reasons, including what helix84 already mentioned. 70.224.53.241 00:14, 26 June 2006 (UTC)[reply]

Rebuilding in Windows

Just wondering, about the rebooting, I didn't know that the kernel in Windows has to be rebuilt before rebooting -- is this true? —The preceding unsigned comment was added by 82.39.136.51 (talk) 12:08, 17 April 2007 (UTC).[reply]

Symbol?

The Linux maintainers tolerate the distribution of proprietary modules, but allow symbols to be marked as only available to GPL modules.

What is a symbol? --Abdull 11:00, 12 November 2007 (UTC)[reply]

Basically, "symbol" means a function (routine) or a variable that has a name and is accessible from other pieces of executable. In other words, "symbols" stand for routines and variables that kernel modules may call/use. Trasz (talk) 15:51, 7 January 2009 (UTC)[reply]

Detail on loading

The current article seems to provide little detail on the actual process of loading and unloading LKMs. Can anyone provide more information on this, even if it has to be OS-specific? « Aaron Rotenberg « Talk « 05:35, 23 January 2008 (UTC)[reply]

Real nature of "tainting"?

Isn't there a category of code that is "open" (in the sense of publicly disclosed) but still "proprietary" (copyrighted or otherwise legally controlled)? Are maintainers put off only by the inability to read the source code, or is there also an issue of tainted "free-ness?" Mrnatural (talk) 19:52, 12 February 2008 (UTC)[reply]

API/ABI stability on FreeBSD

With revert 261265695, the reference to ABI Breakage in RELENG_7 (by a member of the FreeBSD release engineering team) was removed, because "it may not be broken. this was a special case, since it didn't affect anything - no filesystem in ports uses that part of the api." Is there a source for that claim? I do not really question this, because neither UPDATING for RELENG_7 nor the 7.1 release notes contain anything about it and neither the announcement nor the commit message list any real consequences, which I would expect. (Anyhow, I thought rebuilding *-kmod ports would have been necessary.) 85.177.240.32 (talk) 21:14, 3 January 2009 (UTC)[reply]

As far as I know, the only filesystem in the Ports right now is Fuse. And it's not affected, see http://lists.freebsd.org/pipermail/freebsd-stable/2008-July/043974.html. Trasz (talk) 15:57, 7 January 2009 (UTC)[reply]

Section "Security" addendum re: KSplice

Mentioning of a new idea in Linux-Systems to use LKM for hot-patching the kernel might shed a different light on the security of LKM. Or maybe it deserves a entry in See also. 91.37.162.218 (talk) 14:49, 5 July 2009 (UTC)[reply]