- changed status to resolved
Kernel filenames keep growing with every time we install lilo
Issue #26
resolved
When the installer installs lilo, it copies other OS's kernels into /boot/tamu. To accomplish this, it relies on linux-boot-prober proving the path to the kernel, and then copying that file to /boot/tamu and renaming it as "origninal_file_name-sdxx" where sdxx is the partition it is found on.
This creates a problem when it finds a kernel named "linux-2.19.2-sda3" because the resulting file name will be "linux-19.2-sda3-sda3"
To avoid this, simply rename the file "vmlinuz-sdxx" every time.
Comments (2)
-
reporter -
reporter Merged in m0e_lnx/m0e-vinstall (pull request #12)
Several bug fixes and enhancements Fixes
#24. Fixes#25. Fixes#26. Fixes#27→ <<cset e61deccf2f9d>>
- Log in to comment
Fix
#26at VLCore/vinstall. Fix#25at VLCore/Vinstall by checking for /boot/vmlinuz on foreign linux installs before assuming what linux-boot-prober reports→ <<cset b87ff407c89a>>