Skip to contentSkip to conversation

Error in documentation?

DISCUSSION Geoffrey Gallaway 2 participants 2 messages Jun 18, 2001

lore
Share & tools
lore
#0 lore raw

linux/Documentation/modules.txt says that I should find my modules in "linux/modules" after running "make modules". However, this is apparently not true as I see no modules directory.

I am trying to compile a kernel with lots of modules for a machine without a network connection. To move the kernel, I simply copy it to floppy and move it over to the other machine. However, for the modules, is my only choice appears to be "make modules-install" then tar up /lib/modules/kernel-release/ and then remove the directory. Is there a cleaner way to handle this?

Geoffeg

Signature · 3 lines
Geoffrey Gallaway || 
[email protected] || Clones are people two.
D e v o r z h u n ||
#1 lore raw

It does appear that the documentation regarding this is out of date. However, you can still install modules to a given location by:

INSTALL_MOD_PATH="/path/to/modules" make modules_install

Had to dig through the Makefile for that, though it may actually be documented somewhere.

Quoted 10 lines · Geoffrey Gallaway

linux/Documentation/modules.txt says that I should find my modules in "linux/modules" after running "make modules". However, this is apparently not true as I see no modules directory.

I am trying to compile a kernel with lots of modules for a machine without a network connection. To move the kernel, I simply copy it to floppy and move it over to the other machine. However, for the modules, is my only choice appears to be "make modules-install" then tar up /lib/modules/kernel-release/ and then remove the directory. Is there a cleaner way to handle this?

Signature · 3 lines
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
			-- George Orwell