commit 54317145d9469636d89e3bca1d16f7a223315169
parent e5753ab82fb0072d0faefdefc363cc29fe2d7f4e
Author: mayfrost <mayfrost@cock.li>
Date: Sat, 3 Mar 2018 19:28:05 +0000
Update KERNEL.md
Diffstat:
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/KERNEL.md b/KERNEL.md
@@ -119,15 +119,14 @@ Compile and move everything to its place. The "__all__" flag makes modules AND t
* __OPTION B2__: Automatically move kernel to __/boot__ (and in certain distros, symlink the new kernel to __/boot/vmlinuz__ and update the bootloader configuration).
`make install`
+__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__.
+### BUILDING 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__.
`make -j<X> modules`
* Copy generated kernel modules to __/lib/modules/<KERNEL_VERSION>/__.
`make modules_install`
-__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.
-
## INITRD
The __initrd__ is used only while booting, unless you compile the kernel with the filesystem it resides on (__initfs__). There are three options.
* __OPTION 1__: Compile the kernel with support for the filesystem used in the __/boot__ partition (__initfs__).
