::The information should be added ''before'' "Unmount leftovers and reboot" ? The title should mention reboot, by the way. --[[User:DSpider|DSpider]] ([[User talk:DSpider|talk]]) 14:41, 24 September 2012 (UTC)

+

::Shouldn't the information be added ''before'' "Unmount leftovers and reboot" ? By the way, the title should mention rebooting (because most likely there was a kernel update). --[[User:DSpider|DSpider]] ([[User talk:DSpider|talk]]) 14:41, 24 September 2012 (UTC)

Read this first before add new suggestion

Point of this page is to not become another Beginner's guide. It's meant to be a concise checklist of things to be done. So detailed install instruction should go to Beginners' Guide.

If anyone wants to discuss/add something, then do it on Talk:Beginners'_Guide/Installation. An advanced user will find this page less bloated and easier to read, so let's KISS.

GRUB2 Installation

I moved GRUB2 installation after chroot. Otherwise it doesn't work.
grub-bios is in /mnt, so we need to tell grub-install about it.
But arch iso has grub 0.97, and installation - 2.00, so iso's grub doesn't understand installation's files.
--Shuk (talk) 11:42, 23 July 2012 (UTC)

to install grub-bios: install guide say:

Configure the bootloader: refer back to the appropriate article from the bootloader installation section.

GRUB install failure

It looks so similar to the Beginners' Guide as to be almost redundant, but the first subtle difference I came across meant (for me) that this procedure failed where the Beginners' Guide succeeded.

Under "GRUB" you have:

"Install GRUB2 to the harddrive containing your boot partition before you chroot."

# grub-install /dev/sda

doing so returns:

"Path /boot/grub is not readable by GRUB on boot. Installation is impossible. Aborting."

In the Beginners' Guide, this step takes place after chrooting, which (for me) works ok, (although the wording - "Install GRUB2 to the harddrive containing your boot partition before you chroot" - is the same, so I guess both wiki entries are at fault).
--bananabrain

Link Elinks to wiki

Just read that elinks is included on install iso, maybe add an alias/script to allow loading of wiki guide installation guide? --Mr Green

Mention the other config files

The old installation guide said something about editing the other config files:

True, but some clarification somewhere about exactly which bits of rc.conf are still necessary and which have been superceded (and by what) would be useful. So far it seems like just the first six lines of the LOCALIZATION section and the HOSTNAME line from the networking section. I'm still slightly in the dark here, but getting there. --bananabrain

Regarding rc.conf, a lot of information has been added to its man page. I'm not sure how well aligned the man page and wiki page for it are, might need some updating. In any case you don't need to change anything in rc.conf for a basic install, so anything regarding that should go into the Beginners' Guide. --Emiralle (talk) 16:59, 24 July 2012 (UTC)

The rc.conf page will need quite a bit of updating once initscripts >= 2012.07.5-1 moves to [core].

Change section "Connect to the internet"

Since the installation guide is now part of the iso image, I'd like to see a few references to the manpages of the necessary tools here, since you cannot open the network related wiki pages. Maybe something like this would be acceptable:

Assuming a wired ethernet connection, running dhclient or dhcpcd is
sufficient to get a lease. Otherwise set up the connection manually
using ip add, wpa_supplicant (WLAN with WPA), pppoe-setup (DSL), etc.
You can also create and use netcfg profiles. Read more in the manpages:
ip(8), wpa_supplicant(8), pppoe(8), netcfg(8), netcfg-profiles(5)

A reminder to install the packages for the internet connection in the pacstrap section would also be nice. -- progandy

Suggestions to update this guide as part of ISO

Since this guide is now being included as 'install.txt' in the ISO, it might be beneficial to incorporate the following changes:

Entirely remove the 1. Download section and move it to the Download area of the archlinux.org page. This document here is about installing, not downloading, checking, burning discs or dd'ing. The majority of users reading this have likely already booted up the install medium.

Begin or end the document by mentioning the new archlinux(7) man page which explains the location of important system configuration files

# man archlinux

Slightly expand the 6. Connect to the internet section to include the most basic examples of setting up a private network using a dynamic and static IP address. (Right now it's only a single paragraph/line.) It's a vital installation step and should actually be moved to the top as one of the first actions during system setup. This fact should be emphasized.

I can agree to all your suggestions, I wonder why no one is modifying the wiki. Internet connection setup is the most important part and should be covered more extensively. In addition to your changes, mention the manpages and configuration templates for netcfg and pppoe-setup/connect. The boot medium must at least contain easy accesible information in order to read all pages referenced in the installation guide. There should also be mentioned that elinks is installed and can be used to access the wiki. --Progandy (talk) 21:50, 24 August 2012 (UTC)

The dhcpcd network daemon is started automatically: [1], [2], so there's no reason to start it manually. --DSpider (talk) 08:17, 25 August 2012 (UTC)

Keymaps

As this guide mentions the loading of keymaps using loadkeys there should be at least a very small example about /etc/vconsole.conf

Either not talk about keymaps or tell how to make it correct. When this is used as a checklist, the setup of the keymap should not be missing.

add a step: setting the clock

Lots of things care about the clock being more-or-less correct, e.g. pacman-key will not work at all if the clock is too far out. Lots of brand new computers come with the clock set to something in the distant past, which causes weird problems during the install. Thetrivialstuff (talk) 23:14, 31 July 2012 (UTC)

pacman-key --init / populate?

Isn't this a required step? pacstrap does not seem to do it on its own. Thetrivialstuff (talk) 23:15, 31 July 2012 (UTC)

Edit: Ah; I think this was related to the "set the clock" step -- I see that there is a pacman keyring init in the boot sequence of the latest media, but it (silently?) fails if the local clock is wrong.

Link to UEFI Bootloaders page

Instead of telling the user to install GRUB(2) alone in case of UEFI, direct the reader to the UEFI_Bootloaders page which provides info about all the UEFI bootloaders capable of booting linux kernel. Also how can I edit the guide, there is no "edit" tab shown on top of the page. Is this page restricted to few authors only? -- Keshav P R (talk) 15:31, 19 August 2012 (UTC)

Styling

The "Install a bootloader" section should be a bullet point above "Configure the bootloader: refer back to the appropriate ...", no need to have them separate. Using pacstrap to install the bootloader just seems silly (especially since they were also merged in the Beginner's Guide). Also, commands after arch-chroot would look better if they were indented with ": {{bc|# <command>}}", kinda like how # pacman-key -v <iso-file>.sig is at the beginning of the article. Would look much cleaner. --DSpider (talk) 16:33, 20 August 2012 (UTC)

Shouldn't the information be added before "Unmount leftovers and reboot" ? By the way, the title should mention rebooting (because most likely there was a kernel update). --DSpider (talk) 14:41, 24 September 2012 (UTC)