On Fri, May 28, 2010 at 12:45 PM, Volker <reklov@live.com> wrote:

Hello!

I think stumbled across a typo, a missing word and a wrong path in the official Install guide. Can someone check if that's correct?

Subject: [PATCH] Typos and little correction

Fix a typo, a missing word, and correct the path to the installation guide on release media in the info, which is actually /usr/share/aif/docs not /arch. (See the message you get when you run the 2010.05 live media and log in.) ---  doc/official_installation_guide_en |    6 +++---  1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/official_installation_guide_en b/doc/official_installation_guide_en index 01688f6..946a42d 100644 --- a/doc/official_installation_guide_en +++ b/doc/official_installation_guide_en @@ -7,7 +7,7 @@ Patches/comments are welcome on the arch  [releng mailing list](http://www.archlinux.org/mailman/listinfo/arch-releng)  or mail to dieter@archlinux.org

-This guide is available in the /arch directory of release media and on +This guide is available in the /usr/share/aif/docs directory of release media and on  [The arch wiki](http://wiki.archlinux.org/index.php/Official_Arch_Linux_Install_Guide)

 **Related articles** @@ -619,7 +619,7 @@ ever want to use. The majority of your everyday modules will be loaded later  on by udev, during the init process.

 By default, mkinitcpio.conf is configured to autodetect all needed modules for -IDE, SCSI, or SATA systems through so-called HOOKS. The installed should +IDE, SCSI, or SATA systems through so-called HOOKS. The installer should  also have inserted hooks like crypt, lvm, keymap and usbinput if relevant.  This means the default initrd should work for almost everybody.  You can edit mkinitcpio.conf and remove the subsystem HOOKS @@ -834,7 +834,7 @@ You'll notice that in the early userspace (the part that comes after the  bootloader) the hooks (as defined in mkinitcpio.conf) needed to get your root  filesystem are run.  If you have lvm, it will run the lvm hook.  If you use encryption, it will -the keymap and encrypt hooks so you can enter your password to decrypt the +run the keymap and encrypt hooks so you can enter your password to decrypt the  volume.

 Once the system is booted, login as root.  By default the password is empty Also the wiki page would look much better without the <code> tags that markdown put there. ;)

Altogether the new interactive installer is great, especially the support for encryption and LVM, thanks!

These seem right to me. I think Dieter is away for a bit, so it may take a bit to get this merged. I can get to it next week. Thanks for the patch!