2006-05-22 21:00:25 |
Carthik Sharma |
grub-installer: statusexplanation |
Bugzilla status=UNCONFIRMED, product=Ubuntu, component=grub-installer |
Hi,
Thank you for reporting this issue.
Does this problem still occur with the Dapper Beta installer?
|
|
2007-07-31 13:24:19 |
Colin Watson |
grub-installer: statusexplanation |
|
I worked around this in os-prober recently. (Chaining to the other installations rather than copying their boot menu items, as Ian suggests, would still ultimately be better, but is more work to arrange.)
os-prober (1.20) unstable; urgency=low
* Skip grub-installer's "(on /dev/blah)" entries detected in GRUB
configuration files, as if they're useful they will probably be found by
another probe, and detecting them can result in exponential growth of
menu.lst files if you do repeated test installs on multiple partitions.
* Use readlink -f in mapdevfs shim so that os-prober runs outside d-i
handle mount-by-UUID correctly.
* Use mktemp -d rather than /tmp, to make use outside d-i safer.
* Merge from Ubuntu:
- Try to install fs-core-modules and fs-secondary-modules udebs. These
are specific to the Ubuntu kernel udeb layout, but it's fairly cheap
to check for them as well and saves on divergence here.
- Add os-probes/mounted/sparc/80solaris to recognize Solaris/SPARC
(Fabio M. Di Nitto).
- Add linux-boot-probes/mounted/sparc/50silo support (Fabio M. Di
Nitto).
- Try to load ufs module, for Solaris support (Fabio M. Di Nitto).
- Tighten check for whether we're running in d-i; anna-install isn't
quite enough because if you're running d-i code outside d-i it's
sometimes reasonable to install a shim for anna-install.
* Don't probe partitions mounted on /target/boot.
* Teach linux-boot-prober to deal with mounted partitions correctly,
unless they're mounted on /, /target, or /target/boot (LP: #14780). This
should largely obsolete the --mounted option.
* Only use /target/bin/mount if it exists, in order to work better outside
d-i.
-- Colin Watson <cjwatson@debian.org> Thu, 26 Jul 2007 12:33:31 +0100 |
|