Ignore:
Timestamp:
Oct 10, 2006, 6:55:40 PM (18 years ago)
Author:
Chris Staub <chris@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
d8e988ea
Parents:
fa1bdec
Message:

Removed remaining text about compiling keymap into the kernel

File:
1 edited

Legend:

Unmodified
Added
Removed
  • BOOK/bootscripts/common/console.xml

    rfa1bdec rad07557  
    9191EOF</userinput></screen>
    9292
    93   <para>To compile the keymap directly into the kernel instead of setting it
    94   every time from the <command>console</command> bootscript, follow the
    95   instructions given in <xref linkend="ch-bootable-kernel" role="."/> Doing
    96   this ensures that the keyboard will always work as expected, even when
    97   booting into maintenance mode (by passing <option>init=/bin/sh</option> to
    98   the kernel), because the <command>console</command> bootscript will not be
    99   run in that situation. Additionally, the kernel will not set the screen font
    100   automatically. This should not pose many problems because ASCII characters
    101   will be handled correctly, and it is unlikely that a user would need to rely
    102   on non-ASCII characters while in maintenance mode.</para>
    103 
    104   <para>Since the kernel will set up the keymap, it is possible to omit the
    105   <envar>KEYMAP</envar> variable from the
    106   <filename>/etc/sysconfig/console</filename> configuration file. It can
    107   also be left in place, if desired, without consequence. Keeping it could
    108   be beneficial if running several different kernels where it is difficult
    109   to ensure that the keymap is compiled into every one of them.</para>
    110 
    11193</sect1>
Note: See TracChangeset for help on using the changeset viewer.