"McHarry, John" wrote:
>
> I am trying to compile the 2.2.19 kernel one one machine for installation
> on another. I believe I need to do more than just copy over bzImage and
> modify lilo.conf, but I don't know what. Is there documentation somewhere
> on how to do this? Thanks.
This is enough if you don't use modules. If you use modules you
need to copy them too, which is trickier. Several good methods
have been demonstrated, here is another if you can't use the nfs
approach:
1. If you are running the same kernel revision on the compile machine,
temporarily rename /lib/modules/<version> to something else.
Yes - this could be dangerous but tend to work well on a "home
machine"
2. Do the "make modules_install" on the compile machine.
3. Rename the /lib/modules/<version> to something else, and
rename your proper module directory back to what it should be.
4. Transfer the installed module tree to the target machine along with
the bzImage.
The "dangerous part" happens if the kernel on the compile machine
tries to load a module between step 1 and step 3.
This can be avoided in a number of ways, such as:
* Make sure the target and compile machines run different kernel
revisions.
If you're upgrading both, compile for the target machine first.
Or edit the makefile, append something like "target" to the
"extraversion",
you will then get the modules installed in
/lib/modules/<version>target
which is different from what your compile machine uses.
* Use "chroot" so make modules_install will install somewhere else.
info|man chroot for details.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
