From: Serbinenko Vladimir <serbinenko.vova@list.ru>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Scripting and keystrokes
Date: Mon, 13 Jun 2005 21:47:34 +0200 [thread overview]
Message-ID: <42ADE2D6.3030102@list.ru> (raw)
In-Reply-To: <200506132050.05871.okuji@enbug.org>
Yoshinori K. Okuji wrote:
>On Sunday 12 June 2005 10:54, Serbinenko Vladimir wrote:
>
>
>>Which scripting: I propose to make bash-like scripting and make it so
>>close as possible to bash
>>
>>
>
>Agreed.
>
>
>
OK. But question about realization is still open. All ideas are welcome
>>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
>>
>>
>
>Can you describe the expected usage of this? For chain-loading Windows?
>
>
It's useful for loading some OS in special modes when it checks if you
press special key to enter special mode but it goes too fast and you
can't press it fast enough after pressing enter in GRUB.
Often it's failsafe modes. Sometimes I had this problem with windows
when it bugs and I can't enter in failsafe-mode because it goes too fast.
Another usage: chainloading boot-managers.
If you install other manager for special OS you can choose from GRUB
directly the configuration like: down down enter.
Not only boot-managers but also some OS like DOS including FreeDos if
multiple configurations are present in config file.
Ex: As I heard GRUB has problems loading FreeBSD. So you can install
FreeBSD native bootloader even have multiple BSD and/or configurations
and choose it from GRUB.
>Okuji
>
>
>_______________________________________________
>Grub-devel mailing list
>Grub-devel@gnu.org
>http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
>
>
next prev parent reply other threads:[~2005-06-13 20:04 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 ` Scripting and keystrokes Serbinenko Vladimir
2005-06-13 18:09 ` 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 [this message]
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=42ADE2D6.3030102@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.