bootloader looks for vmlinuz1 not vmlinuz
Bug #784234 reported by
danstowell
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bouilloncube |
Fix Committed
|
Critical
|
Aymeric Mansoux | ||
Bug Description
>> ***** Bouilloncube (sh/grub2) runs fine but installs the wrong boot
>> command (looking for vmlinuz1 rather than vmlinuz, and the same for
>> the initrd IIRC). Bootable after editing the command in the
>> bootloader. I haven't looked at the code to see if that's an easy fix.
| Changed in bouilloncube: | |
| importance: | Undecided → Critical |
| milestone: | none → 10.04 |
Revision history for this message
| danstowell (danstowell) wrote | #1 |
Revision history for this message
| Aymeric Mansoux (aymeric) wrote | #2 |
| Changed in bouilloncube: | |
| assignee: | nobody → Aymeric Mansoux (aymeric) |
| status: | New → Fix Committed |
To post a comment you must log in.
OK: in broth, my horrible hacky hook forces the name to "vmlinuz" and "initrd.img", for the reason that they had extra appendages on their names (kernel version? I forget).
http://
There are various places where "vmlinuz" is used.
But there are various places where "vmlinuz1" is used:
/bouilloncube/
/broth/
Can someone suggest what the authoritative approach is? We need to converge on the same filename used in all the scripts but I don't know if there are other factors affecting the naming.