Talk:Installation guide

From ArchWiki
Revision as of 05:45, 6 September 2012 by Fengchao (Talk | contribs) (No mentioning of SWAP: Remove closed.)

Jump to: navigation, search

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)

GRUB install failure

This doesn't work for me.

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

Check MD5 with Windows

Maybe we should add a link to - so people know how to check the MD5 with windows. I would add it myself but the page is locked for edit :-( . --PMay (talk)

This info should be add to Beginner's Guide. -- Fengchao (talk) 03:26, 25 July 2012 (UTC)
QuickSFV is better, IMO. Personally I wouldn't add it at all. Downloading through BitTorrent means that the hash tree is checked, and unless you have a drive with bad sectors (in which case you have bigger issues than this), then you don't really need to verify it. -- DSpider (talk) 07:44, 25 July 2012 (UTC)

The method to set locale

The documentation sais to set the locale by:

  • Set locale preferences in /etc/locale.conf.

The documentation at locale sais that the locale can also be set at /etc/rc.conf. This is confusing and should be clarified. --PMay (talk)

It can be set in both files. The locale.conf file is used by systemd and is more portable across distributions. It's relatively new, so the rc.conf method existed previously (rc.conf is specific to Arch Linux). I think the locale page makes it pretty clear that both can be used. thestinger (talk) 08:27, 26 July 2012 (UTC)

Mention the other config files

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

  • /etc/rc.conf
  • /etc/fstab
  • /etc/mkinitcpio.conf
  • /etc/modprobe.d/modprobe.conf
  • /etc/resolv.conf
  • /etc/hosts
  • /etc/locale.gen
  • /etc/pacman.d/mirrorlist
  • /etc/pacman.conf
  • /etc/crypttab

This guide does not even mention /etc/rc.conf which is one of the central config files of archlinux. That should be added. --PMay (talk)

Well I saw this: Beginners'_Guide#Configure_system so /etc/rc.conf isnot the official way to configure the system anymore... --PMay (talk)
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].
-- Jstjohn (talk) 17:06, 24 July 2012 (UTC)

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 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.

Obtain dynamic IP

# dhcpcd

Set static IP

# ip link set dev eth0 up
# ip addr add dev eth0
# ip route add default via
# echo "nameserver" >> /etc/resolv.conf


  • 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)

Change PS1 during chroot

Be handy for some users to export PS1="[ chroot ]" maybe minor change to arch-chroot script Mr Green

This will never work. PS1 will be overridden by the shell init inside the chroot, which arch-chroot has zero control over. I can't see unknowingly changing the files inside the chroot as being a good idea.


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.

KEYMAP page link added. Close. -- Fengchao (talk) 04:03, 4 September 2012 (UTC)
The section on keymaps and fonts links only to the KEYMAP page. An additional link regarding setting default console font should be added to:

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. --Bluewind (talk) 09:10, 1 August 2012 (UTC)

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)

Add a new language

  • Could someone add the Language ref to the Portuguese version of this guide?


Done. -- Kynikos (talk) 13:08, 20 August 2012 (UTC)
  • Same here for the Romanian translation. Add: [[ro:Ghid de instalare]] above Russian. Thanks! --DSpider (talk) 16:33, 20 August 2012 (UTC)
...and done. -- Kynikos (talk) 13:37, 21 August 2012 (UTC)
Done. -- Kynikos (talk) 09:45, 3 September 2012 (UTC)


  • 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)