On Mon, Dec 17, 2007 at 05:01:42PM +0100, Marco Gerards wrote: > Robert Millan <[EMAIL PROTECTED]> writes: > > > I'd like to move ata.mod initialisation away from its _init routine and into > > a separate command. This way it isn't a nuissance when it gets included in > > monolithic builds (such as the ones made by grub-mkrescue) and disables > > biosdisk > > completely. > > > > Does that sound fine? > > No. What if you put ata.mod in core.img? You would expect your disks > will be detected and that grub.cfg will be loaded immediately. The > user doesn't want to run a command to enable ata.mod and afterwards > load the grub.cfg manually. > > A better solution, IMO, would be changing grub-mkrescue so it doesn't > load all modules.
I'd suggest standarising in something that can work later for keyboards and such. How about: grub-mkrescue --avoid-firmware=disk ? So that we can later add "disk,keyboard,screen" etc, and at the same time it'd also work if grub-mkrescue was implemented for other platforms. -- Robert Millan <GPLv2> I know my rights; I want my phone call! <DRM> What use is a phone call, if you are unable to speak? (as seen on /.) _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
