Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14718 - Insufficient mkinitcpio.conf documentation in beginner's guide, official install guide
Attached to Project:
Arch Linux
Opened by 6hxbghwy (innh4t2w) - Thursday, 14 May 2009, 18:38 GMT
Last edited by Eric Belanger (Snowman) - Friday, 15 May 2009, 19:53 GMT
Opened by 6hxbghwy (innh4t2w) - Thursday, 14 May 2009, 18:38 GMT
Last edited by Eric Belanger (Snowman) - Friday, 15 May 2009, 19:53 GMT
|
DetailsDescription: Info on how to set the correct keymap in mkinitcpio.conf is needed in the beginner's guide and official install guide because otherwise if fsck fails during boot arch asks for root's password for system maintenance, but as the keymap has not been set correctly users of non-US keyboards are unable to log in and fix the system.
http://wiki.archlinux.org/index.php/Beginners_Guide#.2Fetc.2Fmkinitcpio.conf http://wiki.archlinux.org/index.php/Official_Arch_Linux_Install_Guide |
This task depends upon
Closed by Eric Belanger (Snowman)
Friday, 15 May 2009, 19:53 GMT
Reason for closing: Fixed
Additional comments about closing: I fixed the typo in official guide.
Friday, 15 May 2009, 19:53 GMT
Reason for closing: Fixed
Additional comments about closing: I fixed the typo in official guide.
In the configuration files part like in /etc/fstab, same for /etc/mkinitcpio
I think "uou" should be "you"
But the sentence that contains the typo, proves that the guide already contains the info you opened the bug report about, requesting to be added.
So all that is left to do is fix that typo and this bug is fixed.