[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
howtos:slackware:kernel_huge_for_generic [2020/01/02 18:43 (UTC)] – created slackjeff | howtos:slackware:kernel_huge_for_generic [2020/11/07 15:53 (UTC)] – added additional tip for automated execution of mkinitrd_command_generator.sh peter | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== How to switch from Kernel Huge to Generic? ====== | ====== How to switch from Kernel Huge to Generic? ====== | ||
- | At the end of this recipe the user will be able to switch from Kernel | + | At the end of this recipe the user will be able to switch from Kernel |
- | You may be wondering what benefit | + | You may be wondering what benefit |
* More fluidity and faster boot, due to Generic loading only the modules your machine needs. | * More fluidity and faster boot, due to Generic loading only the modules your machine needs. | ||
* The modules are not embedded, thus giving better flexibility. | * The modules are not embedded, thus giving better flexibility. | ||
- | So what is Kernel Huge for? Simple, because it has huge support for many drivers, it is ideal for use in installing the system. Thus allowing to reach a larger number of machines. | + | So what is Kernel Huge for? Simple, because it has huge support for many drivers, it is ideal for use in installing the system. Thus allowing to support |
After installation Huge is no longer needed, which is why we should make the switch. | After installation Huge is no longer needed, which is why we should make the switch. | ||
Line 14: | Line 14: | ||
Login as root, every process will be done by the superuser, after that we will execute the command ' | Login as root, every process will be done by the superuser, after that we will execute the command ' | ||
- | **< | + | < |
- | / | + | / |
</ | </ | ||
- | The output will be from the mkinitrd command with the modules necessary for the operation of your machine. Example: | + | The output will be an example'' |
< | < | ||
Line 38: | Line 38: | ||
</ | </ | ||
- | Copy the entire line where it starts with the command ' | + | Copy the entire line where it starts with the command |
< | < | ||
- | **mkinitrd -c -k 4.4.172 -f ext4 -r /dev/sda1 -m usb-storage: | + | mkinitrd -c -k 4.4.172 -f ext4 -r /dev/sda1 -m usb-storage: |
OK: / | OK: / | ||
Line 53: | Line 53: | ||
</ | </ | ||
- | After that we will enter in lilo the information needed for Kernel Generic to be able to load, you can do this manually or you can simply run the command: '/ | + | <note tip>Tip: the following command will automatically execute the '' |
+ | < | ||
+ | This is useful to execute the command within a script where you can also pass additional parameters such as the partition UUID and a specific file name for initrd.gz: | ||
+ | < | ||
+ | In the note above replace the kernel number, the UUID 32 digits hexadecimal number and the initrd filename based on what you have on you system.</ | ||
+ | |||
+ | After that we will enter in lilo the information needed for Kernel Generic to be able to load, you can do this manually or you can simply run the command: | ||
< | < | ||
- | **/ | + | / |
- | </ | + | |
- | < | ||
image = / | image = / | ||
initrd = / | initrd = / | ||
Line 68: | Line 72: | ||
</ | </ | ||
- | Now let's add the information | + | Now let's add this information |
- | Change the label to a better name like KGeneric | + | Change the label to a better name like " |
< | < | ||
- | **lilo** | + | lilo |
Warning: LBA32 addressing assumed | Warning: LBA32 addressing assumed |