Maybe this isn't the right place, but.. I've been pissed off a couple of times by my grub config being overwritten after installing a new kernel on Ubuntu (presumably the same happens on Debian) - I don't get why it doesn't simply add the new kernel rather than regenerate the entire file?
If you think this is too off-topic then ignore if you will or email me privately :) On 10/15/06, Robert Millan <[EMAIL PROTECTED]> wrote:
Hi there, This is my proposal for a new dessign in update-grub. As you might know, update-grub is a script used in Debian to generate GRUB config file. Over time, we've found that the monolithic dessign of that script made it difficult to maintain and extend, and it ultimately has become bloated. I'm redessigning it to be simple, modular and easily extensible. With this work, we solve another problem: the copyright for original update-grub was held by several people and it was too difficult to attain the paperwork FSF projects require for submitting the script to you. The script I'm attaching is mostly meant as proof of concept to show the proposed framework for generating the config file and allowing third-party apps (memtest86, etc) to hook their stuff in. Please send me your feedback and tell wether you like it. I think it'd be very good if a unified solution for this were provided from GRUB upstream, instead of each distributor cooking up their own. -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
-- Declan Naughton _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel