From: Serbinenko Vladimir <serbinenko.vova@list.ru>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Scripting and keystrokes
Date: Sun, 12 Jun 2005 10:54:25 +0200 [thread overview]
Message-ID: <42ABF841.1050706@list.ru> (raw)
In-Reply-To: <20050609230545.M85450@auto.ucl.ac.be>
Hello all. I'm back. I wrote nothing last time because I was quite busy.
2 themes I'd like to speak of:
1) Scripting: how make it: three possibilities
a) Hand written
b) Bison with 2 branches: one executes directly and other saves the
commands that are for later execution
**UGLY**
c) Convert with bison to the structure like
enum grub_script_cmd_type
{GRUB_SCRIPT_CMD_TYPE_COMMAND,GRUB_SCRIPT_CMD_TYPE_FOR_IN, <...>};
struct grub_script_for_in
{
char *var;
char **list;
grub_script_cmd *loop_begin;
grub_script_cmd *skip_loop;
}
struct grub_script_cmd
{
grub_script_cmd_type type;
union
{
char *command;
grub_script_for_in for_in;
<...>
}
}
*GOOD SOLUTION IMHO*
Which scripting: I propose to make bash-like scripting and make it so
close as possible to bash
2) Keystrokes: emulation of keypress: just write keys in buffer before
booting. I propose to add array of functions grub_preboot that will be
launched between grub_machine_fini and grub_loader_boot_func and
functions grub_add_preboot and grub_remove_preboot
And command syntax like:
keystroke [<first key> [<second key> [...]]]
Example
keystroke h e l l o
Space is needed because some keys can't be written with one symbol like:
F1, insert, ...
ex:
keystroke F8 down enter
I'm ready to write both scripting and keystroke.
Vladimir
Serbinenko
next prev parent reply other threads:[~2005-06-12 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 13:48 network support : memory management problem Vincent Guffens
2005-05-31 16:45 ` Vincent Guffens
2005-05-31 17:08 ` Marco Gerards
2005-06-06 10:03 ` Vincent Guffens
2005-06-08 19:38 ` Marco Gerards
2005-06-09 23:09 ` Vincent Guffens
2005-06-12 8:54 ` Serbinenko Vladimir [this message]
2005-06-13 18:09 ` Scripting and keystrokes Serbinenko Vladimir
2005-06-13 18:52 ` Yoshinori K. Okuji
2005-06-13 19:39 ` Serbinenko Vladimir
2005-06-13 18:50 ` Yoshinori K. Okuji
2005-06-13 19:47 ` Serbinenko Vladimir
2005-05-31 22:56 ` network support : memory management problem Yoshinori K. Okuji
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=42ABF841.1050706@list.ru \
--to=serbinenko.vova@list.ru \
--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.