mirror of
https://github.com/mayfrost/guides.git
synced 2024-11-28 02:11:46 +00:00
Update KERNEL.md
This commit is contained in:
parent
e5753ab82f
commit
54317145d9
@ -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).
|
* __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`
|
`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
|
### 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__.
|
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`
|
`make -j<X> modules`
|
||||||
* Copy generated kernel modules to __/lib/modules/<KERNEL_VERSION>/__.
|
* Copy generated kernel modules to __/lib/modules/<KERNEL_VERSION>/__.
|
||||||
`make modules_install`
|
`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
|
## INITRD
|
||||||
The __initrd__ is used only while booting, unless you compile the kernel with the filesystem it resides on (__initfs__). There are three options.
|
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__).
|
* __OPTION 1__: Compile the kernel with support for the filesystem used in the __/boot__ partition (__initfs__).
|
||||||
|
Loading…
Reference in New Issue
Block a user