[10.10 - Alpha 3 (candidate)] Prompts misleading grub dialogs during UEC Node installation.
Bug #613463 reported by
Dave Walker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
grub2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
bzr1218-0ubuntu1 introduced a new depends for the node controller. This causes two dialogs to be presented to the installer, but it seems the data isn't really required and the real grub installation is handled later (end of process).
The first one asks for a "Linux Command", which can be left blank.
The second, more concerning one is grub asking which device you want grub installed on. When selecting a device, grub returns a confirmation that "you don't want to install grub?".. This is false, as it can be safely ignored.
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: iso-testing |
tags: | added: maverick |
affects: | grub (Ubuntu) → grub2 (Ubuntu) |
To post a comment you must log in.
This bug is present now because eucalyptus-nc added a dependency on grub-pc. I believe that this caused grub-pc to get installed earlier in the installation process, before some other things were properly set up.
The reason for the dependency on grub-pc is that eucalyptus-nc is creating a boot floppy (no, I'm not kidding) using grub-mkrescue. That is done in mk-mb-loader [1]. grub-rescue depends on a functional grub-mkimage, and to create bootable content for a "pc" system, that depends on files inside grub-pc (the content of /usr/lib/ grub/i386- pc/).
One solution to this would be to provide the contents of /usr/lib/ grub/i386- pc in a separate package , and maybe in general all of the /usr/lib/ grub/<format> directories. Ie, if there was a package called grub-pc-modules, then eucalyptus-nc could depend on that package and on grub-common (for grub-rescue). That would have the added benefit of not explicitly requiring a bootloader in eucalyptus-nc (for a case where grub-pc wasn't the right boot loader for the host system).
It seems to me that the content of /usr/lib/grub/<dir> is useful of simply being a host's bootloader. It may well make sense to have all of /usr/lib/grub/* installed on a system, but grub not used as the host's bootloader at all.
-- bazaar. launchpad. net/~ubuntu- core-dev/ ubuntu/ maverick/ eucalyptus/ devel/annotate/ head%3A/ tools/mk- mb-loader
[1] http://