New kernel install does not run update-burg

Bug #594431 reported by David Clayton
This bug affects 13 people
Affects Status Importance Assigned to Milestone

Bug Description

In my Ubuntu 10.04 system a new kernel installed via the Update system did not run update-burg, it still ran update-grub because the burg install did not modify the /etc/kernel-img.conf file to suit.

Here is my /etc/kernel-img.conf with the changes that now should work:

do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-burg
postrm_hook = update-burg

I would suggest that the original /etc/kernel-img.conf be saved during burg install and restored if burg is subsequently removed.

Revision history for this message
Miroslav Hadzhiev (xtigyro) wrote :

Yes, so the boot menu is not updated. Today I installed kernel 2.6.35-rc1 for Lucid (from the mainline PPA - and the kernel cannot be booted.

I tried this work-around:

1. completely deinstalled BURG
2. reinstall GRUB (so that the new kernel is recognized)
3. install BURG again


Revision history for this message
bean (bean123ch) wrote :

No need for such trouble, running 'sudo update-burg' will suffice.

A better solution is to modify /etc/kernel-img.conf so that update-burg would be run automatically, as indicated in the first thread. Although I don't know if it's standard behavior for the package installer to make the change directly, since /etc/kernel-img.conf don't belongs to burg after all.

Revision history for this message
David Clayton (dcstar) wrote :

Perhaps the burg install could replace the expected "update-grub" script with a soft link to "update-burg"?

Grub does not have to be installed anyway (there are other bootloaders), so perhaps there is no problem altering that /etc/kernel-img.conf file anyway (on the assumption other bootloaders need the same functionality and may well alter that file themselves).

Revision history for this message
bean (bean123ch) wrote :

I think it's better not to replace update-grub. grub2 and burg can coexist, user can switch between them by writing the boot code with grub-install or burg-install. If update-grub is changed to update-burrg, then grub2 will stop working.

As for the entry in /etc/kernel-img.conf, perhaps a better solution is to use script update-bootloader, which calls both update-grub and update-burg. This way we can make sure kernel change will be known to both loader.

Revision history for this message
Praveen Thivari (praveenthivari) wrote :

If u dont want to edit by default then it would be a better option tht during installation u provide a option to enable it. So, u are not doing anything, it will depend on user's descrition

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.