Hi, I see the main objection here is about too many new modules, and the use of script to configure boot process. But how about the new parser/reader/menu_viewer model ? If I put them back in one normal.mod, but keep the parts separated in source, would that be acceptable ?
Also, some thoughts about grub2 authority. I do understand the needs to keep source clean and safe for a boot loader, but sometimes the process just seems too slow. For example, Colin's graphic menu patch has been pending for almost half a year. IMO, if a patch implement a generally useful feature, have no serious design faults, and don't conflict with other parts of grub2, then it's safe to commit. For small issues, we could fix it later. Perhaps we can add a testing branch, in which developers have more freedom to commit their work. The maintainer can review them periodically and merge selected parts with the main branch. Many open source project have more than one branches, perhaps it'd work with grub2 as well. -- Bean _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel