Bootloader Manager does not cooperate with update-grub

[Jimmy Rönnholm]

Editing of individual boot entries has a tendency to conflict with the way update-grub does things.
In particular, update-grub overwrites the ones before the ### END DEBIAN AUTOMAGIC KERNELS LIST line.
I have written more in detail about it here if you are interested:
http://jronnholm.blogspot.com/2007/09/taking-look-at-bootloader-manager.html

If you have a good solution to this problem in the works, I would love to hear about it since I am the developer of a similar application.

[Tomé Vardasca (cacau)]

Thanks for the review of my project. The initial bugs that you shown, I have correct them, but I forget to upload them to launchpad, so great work reminding me.
My application cooperate little with update-grub script but only when the user deletes all the recovery and memtest entries, then change the automagic var s and when the update-grub rus it dont add this entries.
Another thing you say is that the app change all the file, is a way to the file is remaining clean, and when you are editing it if your computer crashes for some reason he didnt change the file.
The grubconfig list are there for, when update-grub runs, it erases the user custom options of the kernel and the title too, so when the user installs a new kernel, apt runs my app in command line and ensure if there are any kernel was updated, and restore the kernel options and title. I've tested it and works well.

[Tomé Vardasca (cacau)]

You could discuss a good solution with Martin Böhm, he help me with the grubconfig backend.
Cheers,
Tomé Vardasca

[Jimmy Rönnholm (jronnholm)]

Ok, it is good that you are aware of the update-grub issues.
My main concern was that I did not want to see another new project go and implement a lot of features,
and then run into update-grub so the efforts will be wasted and/or the project stalled like kubuntu-grubconfig:
https://blueprints.launchpad.net/ubuntu/+spec/kubuntu-grubconfig

My other concern was that I have had a lot of bug reports about my tool messing up the users menu.lst, for example removing custom boot entries.
Since my tool relies on update-grub on systems based on Debian and/or with grub2 installed, it has in fact been update-grub that "messed" with the menu.lst.
The real problem has been that the user had edited the menu.lst to remove "comments" and change the boot options.

A problem I can foresee is that a user uses bootloader-manager to change some settings, then the user tries startup-manager(my tool), my tool calls update-grub and suddenly I will get bug reports about my tool removing the settings your tool made. :(

My problem with the file being reorganized is not really that serious. It is more of a cosmetic issue.

Anyway, feel free to close this bug if you wish.