| 1 |
"Gordon Gallup" <gallup.gordon@×××××.com> posted |
| 2 |
d9edbc030605261404o889e945j7929b42f62b38ed@××××××××××.com, excerpted |
| 3 |
below, on Fri, 26 May 2006 16:04:28 -0500: |
| 4 |
|
| 5 |
> what is the difference *.o and *.ko modules? |
| 6 |
|
| 7 |
*.ko indicates a kernel module from a 2.6 series kernel. It was changed |
| 8 |
to distinguish it from *.o, which more commonly is an intermediate step |
| 9 |
(the unlinked binary object file) in compilation (using gcc or the like). |
| 10 |
Previous to the 2.6 kernel series, they used *.o, and it's possible that |
| 11 |
generated a number of bug reports where the user got confused and tried to |
| 12 |
use an object file as a kernel module. Switching to *.ko for the |
| 13 |
completed kernel modules eliminates that confusion. |
| 14 |
|
| 15 |
-- |
| 16 |
Duncan - List replies preferred. No HTML msgs. |
| 17 |
"Every nonfree program has a lord, a master -- |
| 18 |
and if you use the program, he is your master." Richard Stallman |
| 19 |
|
| 20 |
-- |
| 21 |
gentoo-amd64@g.o mailing list |
Archives