| Summary: | catalyst: multiple vmlinuz-* files causes grub.cfg generation to make insane cfg | ||
|---|---|---|---|
| Product: | Gentoo Hosted Projects | Reporter: | Mason Rocha <turret> |
| Component: | Catalyst | Assignee: | Gentoo Catalyst Developers <catalyst> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | azamat.hackimov |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
- sys-kernel/gentoo-kernel-bin had installed two vmlinuz-* files (one normal, one ending in .old) - L82 of targets/support/functions.sh fails to rename kernel image quietly (makes some noise but doesnt cause crash) due to -e only accepting 1 argument - vmlinuz-* file not renamed to /boot/{kernel_name} - bootloader script autogenerates grub.cfg to point at /boot/{kernel_name}, assuming file exists - grub requires manual intervention to boot at this stage due to /boot/{kernel_name} not existing same issue likely exists at L73-L95 of the file where similar syntax is used underlying issue that distkernels' files are not managed at all prior to installation to /boot