From: Gene Czarcinski <gczarcinski@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: multi-boot
Date: Fri, 13 Jun 2014 12:14:00 -0400 [thread overview]
Message-ID: <539B2348.80902@gmail.com> (raw)
In second 5.3 of the GNU GRUB 2.00 manual, there is a statement
"Currently autogenerating config files for multi-boot environments
depends on os-prober and has several shortcomings."
I agree. Os-prober and the way it works with 30_os-prober is fragile at
best and sometimes produces incorrect configurations.
Personally, I use a variation of the manually configured option
described in section 5.3: I install a very small system and then use
/etc/grub.d/40_custom to provide my multi-boot options ... mostly by
chainloading configfile.
In section 5.3, there is also mention of "fixing it is scheduled for the
next release" and "it" refers to os-prober. OK, what is the story? Is
anything being done to improve easy configuration for multi-boot?
Just what is the status of using/depending-on os-prober?
Some distributions such as SUSE, Fedora, RHEL, Ubuntu (?) believe that
users want some type of auto-config which enables them to bootup their
old systems when a new install replaces the MBR and points to this newly
install system.
Comments?
Gene
next reply other threads:[~2014-06-13 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 16:14 Gene Czarcinski [this message]
2014-07-23 7:38 ` multi-boot Vladimir 'φ-coder/phcoder' Serbinenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=539B2348.80902@gmail.com \
--to=gczarcinski@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).