From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [RFC] Support for UEFI ESP in os-prober
Date: Wed, 5 Jun 2013 21:58:15 +0400 [thread overview]
Message-ID: <20130605215815.10b7954b@opensuse.site> (raw)
In-Reply-To: <51AF73B2.5070109@gmail.com>
В Wed, 05 Jun 2013 12:21:54 -0500
Bruce Dubbs <bruce.dubbs@gmail.com> пишет:
> Mads Kiilerich wrote:
> > On 05/31/2013 07:03 PM, Bruce Dubbs wrote:
> >> Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> >>
> >>> I must say I'm generally disappointed with os-prober and have
> >>> ideas to move away from it. I'll start another topic for it.
> >>
> >> I agree. I would prefer adding an include command so grub.cfg could
> >> just do something like:
> >>
> >> include /boot/grub/grub.d/*.cfg
> >>
> >> and have an install procedure drop in one or more menu items instead
> >> of every os install or update rewriting the entire grub.cfg every time.
> >
> > http://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ describes
> > such a configuration structure, and
> > http://pkgs.fedoraproject.org/cgit/grub2.git/plain/0362-blscfg-add-blscfg-module-to-parse-Boot-Loader-Specif.patch
> > implements it as a grub command.
>
> Although that's a good start, it seems a little too specific. What I
> had in mind would be the equivalent to the source command in bash.
grub already has "source" command.
> For
> example,
>
> if condition; then
> include (hd0,3)/grub/custom/themes/themeA.cfg
> else
> include (hd0,2)/boot/grub/themes/themeB.cfg
> fi
>
> # Get menuentries
> include /boot/grub/grub.d/*.cfg
>
Implementing full-fledged globbing in grub is probably overkill; adding
"source_dir" command looks more doable. Something like
source_dir --suffix .cfg /boot/grub/grub.d
Any takers? :)
next prev parent reply other threads:[~2013-06-05 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 15:04 [RFC] Support for UEFI ESP in os-prober Andrey Borzenkov
2012-09-30 20:30 ` yannubuntu
2012-10-01 11:25 ` Vladimir 'phcoder' Serbinenko
2013-05-31 14:48 ` Andrey Borzenkov
2013-05-31 16:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-31 17:03 ` Bruce Dubbs
2013-05-31 17:55 ` Chris Murphy
2013-06-05 15:56 ` Mads Kiilerich
2013-06-05 16:56 ` Andrey Borzenkov
2013-06-05 17:21 ` Bruce Dubbs
2013-06-05 17:58 ` Andrey Borzenkov [this message]
2013-06-05 18:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-06-05 18:53 ` Bruce Dubbs
2013-06-05 19:03 ` Andrey Borzenkov
2013-06-05 19:29 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-06-05 17:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] <mailman.26139.1370458399.22519.grub-devel@gnu.org>
2013-06-06 15:33 ` Tom Davies
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=20130605215815.10b7954b@opensuse.site \
--to=arvidjaar@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).