- Timestamp:
- 06/20/2004 02:38:21 PM (20 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- de1b856
- Parents:
- a942c0a
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/console.xml
ra942c0a r19afc4e 96 96 instructions are given in <xref linkend="ch-bootable-kernel"/>. Doing this 97 97 ensures that your keyboard will always work as expected, even when you boot into 98 maintenance mode (by passing <parameter>init=/bin/sh</parameter> to the kernel), as in that 99 situation, the <command>console</command> bootscript won't be run.</para> 98 maintenance mode (by passing <parameter>init=/bin/sh</parameter> to the kernel), 99 as in that situation, the <command>console</command> bootscript won't be run. 100 Additionally, the kernel will not set the screen font automatically. Again, 101 this shouldn't pose too many problems as ASCII characters will still be handled 102 correctly, and it is unlikely that you would need to rely on non-ASCII 103 characters whilst in maintenance mode.</para> 100 104 101 105 <para>Since the kernel will set up the keymap, you can omit the KEYMAP variable
Note:
See TracChangeset
for help on using the changeset viewer.