Slackware Documentation Project, "How to switch from Kernel Huge to Generic" seems to have bugs.

How to switch from Kernel Huge to Generic
https://docs.slackware.com/howtos:sl...ge_for_generic

I think I've nailed the problem down to "/usr/share/mkinitrd/mkinitrd_command_generator.sh -l \ /boot/vmlinuz-generic-4.4.172" (the lilo.conf generator), seems to be also re-running mkinitrd and re-editing what the previous mkinitrd_command_generator.sh incanatation wrote. This can be witnessed by the comment written by the lilo.conf generator, which omits many of the options utilized within my previously executed mkinitrd execution incanatation.

I have so far verified this, or worked around this problem, by re-running the mkinitrd_command_generator.sh incanatation. I have yet to perform multiple executions for verifying this bug, but am pretty sure with a fully booted mkinitrd after several hours, that this is the problem.

Not sure if this an upstream bug, where the "-l" switch is not suppose to overwite the mkinitrd tree/image, without the use of "-c" (clean mkinitrd tree) option.

Can I also suggest, a clean-up of this documentation, more clearly/consicely writing only the steps needed for a successful mkinitrd execution/install, and clearly separating some of the included hints/notes/explanations causing confusion? In other words, a lot of the explanations do not have enough uniform white space, for people to clearly see only the commands needed for successfully executing/acquiring mkinitrd images.

I am sorry to disappoint, but the "mkinitrd_command_generator.sh" script does not execute any "mkinird" command. The script will only show you what it thinks is a suitable "mkinitrd" command for your specific hardware configuration.
Perhaps you need to be more specific in your observations - for instance show us the commands you entered and the results they yielded.

As for "cleaning up" the documentation, I do not understand what you are referring to. YEs, this is a translation into English from another language and the author's grasp of English language is not the best, but it is understandable.
White space issues? How are you reading this article in the Wiki? Graphical browser or a text-based browser such as Lynx?

I already understand "mkinitrd_command_generator.sh" is a command line mkinitrd incanatation generator.

Here's my version of instructions, of course, using the previous cite's information.


For generating mkinitrd incanatations, use the interactive mkinitrd_command_generator.sh menus using "mkinitrd_command_generator.sh -i" option.
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -i

Once a mkinitrd incanation is printed, copy and edit the incanatation as needed, then execute. For example:
# mkinitrd -c -k 4.4.240 -f ext4 -r /dev/sda2 -m jbd2:mbcache:ext4 -h /dev/sda1 -u -o /boot/initrd.gz

Check to ensure /boot/initrd.gz is updated, usually not needed.
# ls -al /boot/initrd.gz

If this is the first time using a newer kernel or have not already made an entry within lilo.conf with updated kernel version numbers, then execute the following. A new entry will be added to the bottom of /etc/lilo.conf. Edit the entry as needed.
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-4.4.240 >> /etc/lilo.conf

Edit /etc/lilo.conf as needed, then re-install/recycle writing lilo to MBR:
# lilo

I see no bugs in the how-to.

mkinitrd_command_generator.sh produces what it is supposed to
As does mkinitrd_command_generator.sh -l /boot/vmlinuz
Nothing is overwritten. What is shown here is the recommended command to usage for mkinitrd and a recommend /etc/lilo.conf entries based on the passed kernel.

If the page your referring to had a bug, you would not be the only person who is having trouble changing to a generic kernel.

When first mentioned in your link the bit of code isn't present.

It is present on that page.
Perhaps you are referring to the missing '\' for @rogerxx's post.
The '\' is not needed.

Another possibility, lilo might not have been writing to MBR due to a lilo.conf error.

I could have been missing the failure due to lilo's tame error messages. Caught myself ignoring lilo's error messages the other night.

I think my instructions within Comment #4 are more simple and concise.