bootloader looks for vmlinuz1 not vmlinuz

Reported by danstowell on 2011-05-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bouilloncube
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.

danstowell (danstowell) on 2011-05-17
Changed in bouilloncube:
importance: Undecided → Critical
milestone: none → 10.04
danstowell (danstowell) wrote :

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://bazaar.launchpad.net/~puredyne-team/broth/devel/revision/475#stock/binary_local-hooks/renamebootimage.sh
There are various places where "vmlinuz" is used.

But there are various places where "vmlinuz1" is used:
/bouilloncube/sh/grub2/grub-puredyne-1010.cfg.in
/broth/stock/binary_local-includes/extra/*/*

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.

Aymeric Mansoux (aymeric) wrote :

I renamed the grub templates to vmlinuz and initrd and commited.

no need to bother too much with this as we release Puredyne with only one kernel, so let's stick to normal naming scheme.

Changed in bouilloncube:
assignee: nobody → Aymeric Mansoux (aymeric)
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers