All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: booting another system from running linux (kexec)
Date: Fri, 24 Sep 2004 09:01:19 +0000	[thread overview]
Message-ID: <87sm98kpls.fsf@marco.marco-g.com> (raw)
In-Reply-To: <20040924020644.6c89aa25.jrydberg@night.trouble.net> (Johan Rydberg's message of "Fri, 24 Sep 2004 02:06:44 +0200")

Johan Rydberg <jrydberg@night.trouble.net> writes:

> Tomas Ebenlendr <ebik@artax.karlin.mff.cuni.cz> wrote:
>
> : Scripting and dhcp are both issues that we want in grub2. [...]
>
> Have there been any discussion on how the scripting language will look
> like?  Will it be a simple language, specific to GRUB2, or will it
> some other language be re-used.

No, there was not much discussion about this.

> I would love to see a powerful scripting language, something like
> Scheme.  But I'm not sure how usefull it would be.  Scheme is a very
> simple, but yet powerful language that can very well be used for
> scripting.  I'm not sure, though, that it fits into the context of
> GRUB2.

IMHO something bash-like would be the best.  Everyone knows these kind
of languages.  And the config file will look a lot like the one of
GRUB Legacy.

That is the problem of scheme, most people don't know it.  For me it
is important that someone who wants a simple scripting feature don't
have to learn a completely new language.  I assume most uses of GRUB
are not programmers.

Thanks,
Marco






  reply	other threads:[~2004-09-24  9:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 15:49 booting another system from running linux (kexec) Gerd v. Egidy
2004-09-23 19:30 ` Tomas Ebenlendr
2004-09-24  0:06   ` Johan Rydberg
2004-09-24  9:01     ` Marco Gerards [this message]
2004-09-24  9:40   ` Gerd v. Egidy
2004-09-24  9:54     ` Marco Gerards

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=87sm98kpls.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --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.