From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Adding support for top grub menu
Date: Sun, 09 May 2010 17:11:14 +0200 [thread overview]
Message-ID: <4BE6D092.5020601@gmail.com> (raw)
In-Reply-To: <AANLkTikr2cfSxHBZPJDLcWATH1t4zvfXSxhXPrGd6qGK@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
Jarno Suni wrote:
> 2010/5/9 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>
>
>> I don't understand what you're exactly saying but if you install
>> os-prober grub will discover other OS in update-grub.
>>
>
> But if you use os-prober, I suppose it finds all kernels installed in
> all distributions and makes the grub menu too big. And the
> distributions found by os-prober can not update the grub menu, when
> they get new kernel.
>
>
> I want to chainload grubs to make menus more tidy and modular, but
> installing the top grub could be more elegant.
>
> The top menu grub partition is independent of the operating system
> installed so the menu would continue to exist even if all partitions
> of all distributions and other operating systems were reformated; on
> the other hand any linux distribution that has grub 2 could be used to
> maintain the top grub. My approach uses chainloading grubs, but if I
> have understood correctly, installing to boot sector of a partition is
> not recommended.
>
>
For this case install tools to generate grub.cfg for each distro without
installing actual grub and then in main grub.cfg:
menuentry "OS 1" {
search -s -l <label1>
configfile /boot/grub/grub.cfg
}
...
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-05-09 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 12:20 Adding support for top grub menu Jarno Suni
2010-05-09 14:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-09 14:56 ` Jarno Suni
2010-05-09 15:11 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-05-15 11:33 ` Jarno Suni
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=4BE6D092.5020601@gmail.com \
--to=phcoder@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.