commit 66c58d1aad6c13cc86158e13400133a7a93408c2 parent ade1235cfa14ef2c7bb5198e0431f0ec67eeccaa Author: mayfrost <mayfrost@cock.li> Date: Sat, 3 Mar 2018 19:33:32 +0000 Update KERNEL.md Diffstat:
| M | KERNEL.md | | | 3 | ++- |
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/KERNEL.md b/KERNEL.md @@ -122,7 +122,8 @@ Compile and move everything to its place. The "__all__" flag makes modules AND t __NOTE__: The __vmlinuz__ can be any name but that exact name has to be added to the configuration file of your bootloader of choice. Usually a version number is appended to the new kernel image. This has the advantage to avoid replacing a current kernel and having a fallback as backup to boot. You can set to boot from any image in the bootloader once you configure them in the bootloader. ### BUILD MODULES -Compile individual files for each question you answered M during kernel config. The object code is linked against your freshly built kernel. (For questions answered __Y__, these are already part of __vmlinuz__, and for questions answered __N__ they are skipped). Modules end with __.ko__. +Modules end with __.ko__. They are individual files for each question you answered __M__ during kernel configuration. The object code is linked against your freshly built kernel as separate modules. Questions answered __Y__ were integrated into the kernel (__vmlinuz__), and for questions answered __N__ they were skipped (not compiled). +* To compile modules. `make -j<X> modules` * Copy generated kernel modules to __/lib/modules/<KERNEL_VERSION>/__. `make modules_install`