* docs/grub.texi: Correctly use "terminal_input" and not "terminal" in
the example.
This commit is contained in:
parent
5d8031749e
commit
e1ad0edd11
2 changed files with 6 additions and 1 deletions
|
@ -1,3 +1,8 @@
|
|||
2011-03-30 Vladimir Serbinenko <phcoder@gmail.com>
|
||||
|
||||
* docs/grub.texi: Correctly use "terminal_input" and not "terminal" in
|
||||
the example.
|
||||
|
||||
2011-03-30 Vladimir Serbinenko <phcoder@gmail.com>
|
||||
|
||||
* grub-core/term/at_keyboard.c (set_scancodes)
|
||||
|
|
|
@ -1998,7 +1998,7 @@ The commands @command{terminal_input} (@pxref{terminal_input}) and
|
|||
@command{terminal_output} (@pxref{terminal_output}) choose which type of
|
||||
terminal you want to use. In the case above, the terminal will be a
|
||||
serial terminal, but you can also pass @code{console} to the command,
|
||||
as @samp{terminal serial console}. In this case, a terminal in which
|
||||
as @samp{terminal_input serial console}. In this case, a terminal in which
|
||||
you press any key will be selected as a GRUB terminal. In the example above,
|
||||
note that you need to put both commands on the same command line, as you
|
||||
will lose the ability to type commands on the console after the first
|
||||
|
|
Loading…
Reference in a new issue