puredyne-team team mailing list archive

[danstowell <784234@xxxxxxxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of puredyne
team, which is the registrant for bouilloncube.
https://bugs.launchpad.net/bugs/784234

Title:
  bootloader looks for vmlinuz1 not vmlinuz

Status in bouillon cube:
  New

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.