"How to switch from Kernel Huge..." mkinitrd bugs
by rogerxx from LinuxQuestions.org on (#5EC5Z)
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.
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.