All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Some ideas about new features of grub
Date: Tue, 7 Jul 2009 20:39:33 +0200	[thread overview]
Message-ID: <20090707183933.GA14645@thorin> (raw)
In-Reply-To: <ca0f59980907042013r468ae1a6g668110fcf3f0c4e1@mail.gmail.com>

On Sun, Jul 05, 2009 at 11:13:25AM +0800, Bean wrote:
> Hi,
> 
> >> LUA integration.
> >> LUA is quite powerful, it's more suitable to do complicated task than
> >> sh script. For example, we can use it to detect os at runtime,
> >> implement simple commands, or draw the graphic menu.
> >
> > I don't mind LUA being supported, but I think it's unnecessarily big
> > for the task GRUB is usually going to perform (the canonical example
> > of that is in the default grub.cfg) in the majority of cases.  I'd
> > like to see *that* use case made more robust instead of switching to
> > something else to obtain a flexibility we don't currently need.
> 
> With LUA, we can have a more user friendly interface. I like way rEFIt
> works, it doesn't require configuration. At runtime, it detects os and
> shows an icon for each of them. We can achieve similar goal using lua.
> Of course, advanced user can write the menu manually, but for most
> user, a smart auto-generated menu may be more appealing.

But we have grub-mkconfig for that.  This is what distributions shipping
GRUB are using.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-07-07 18:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  8:48 Some ideas about new features of grub Bean
2009-07-02 17:51 ` Pavel Roskin
2009-07-02 18:38   ` Duboucher Thomas
2009-07-02 20:44     ` Pavel Roskin
2009-07-02 19:38   ` Vladimir 'phcoder' Serbinenko
2009-07-02 21:23     ` Pavel Roskin
2009-07-02 21:37       ` Vladimir 'phcoder' Serbinenko
2009-07-04  4:57         ` Pavel Roskin
2009-07-31  8:18   ` Marco Gerards
2009-07-04 20:18 ` Robert Millan
2009-07-05  3:13   ` Bean
2009-07-07 18:39     ` Robert Millan [this message]
2009-07-08  6:19       ` Pavel Roskin
2009-07-10 17:11         ` Robert Millan
2009-07-10 21:27           ` BandiPat
2009-07-11  6:53             ` Bean
2009-07-11 16:20               ` Michal Suchanek
2009-07-11 18:32                 ` Colin Watson
2009-07-11 18:55                   ` Robert Millan
2009-07-11 18:33                 ` Felix Zielcke
2009-07-11 18:27               ` Robert Millan
2009-07-12 13:40               ` Pavel Roskin
2009-08-23 12:55 ` Robert Millan
2009-08-23 12:56 ` Robert Millan
2009-08-23 15:22   ` adrian15
2009-08-23 16:58     ` Vladimir 'phcoder' Serbinenko
2009-08-23 23:02       ` Robert Millan
2009-09-11 21:48   ` Pavel Roskin

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=20090707183933.GA14645@thorin \
    --to=rmh@aybabtu.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.