Talk:Installation guide

From ArchWiki
Revision as of 02:26, 14 January 2015 by Sudokode (talk | contribs) (→‎Firewall: new section)
Jump to navigation Jump to search

Read this first before adding new suggestions

  • The point of this page is to not become another Beginners' guide. It is meant to be a concise checklist of things to be done. So, detailed installation instructions should go to Beginners' guide.
  • If there is something to discuss which should also affect the Beginners' guide, then do it on Talk:Beginners' guide. An advanced user will find this page less bloated and easier to read, so let's KISS.

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)
Yes and no. "Configure the network again for the newly installed environment: see Network configuration and Wireless network configuration." implies that if it worked on the install iso, it should also work after install. A sentence that says explicitly that even if it needed no config earlier, now it does need a config (and this config is usually bringing up the ethernet interface, i.e., one "ip link set eth0 up" followed by a "dhcpcd eth0") would save a lot of people time. Iaw4 (talk) 13:07, 20 December 2014 (UTC) iaw4
Moving the "Download" section to should be discussed in a bug report. Anyway I disagree, as downloading is part of the whole installation procedure, from scratch to the login screen in the new system. If by "installing" we meant only extracting the packages, we should also move all the configuration part to another article.
I've mentioned archlinux(7) in the intro.
Network configuration instructions will not be expanded because they would duplicate too much of the linked articles. Those who find consusing the fact that configuring the network in the chroot is different from configuring it in the live system should follow the Beginners' guide instead.
If you want elinks to be mentioned in the install.txt in the installation system, please submit a patch for . Mentioning it in this article would be nonsensical, since whoever visits it is already using a browser.
-- Kynikos (talk) 03:29, 21 December 2014 (UTC)

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)

I agree, the instructions in "Installation Guide" leaves you without a /etc/adjtime file. The following should be added (taken from beginners guide, but shortened): Set the hardware clock and generate a /etc/adjtime file with # hwclock --systohc --utc or # hwclock --systohc --localtime Bwid (talk) 08:03, 3 March 2013 (UTC)

There's no need for an adjtime file, but it does make sense to have people use timedatectl from the live media to set the clock correctly. -- thestinger (talk) 03:30, 15 March 2013 (UTC)

Proposed changes to Beginners' Guide and link to Post-Installation

Some major changes are under discussion in Talk:Beginners'_Guide#Guide_restructuring: some of them would require adjustments to this very guide, see for example this post.

Please reply in the linked discussion, not here.

-- Kynikos (talk) 12:15, 22 September 2012 (UTC)

I've added the steps in Beginners' Guide/Post-Installation to this guide, which now directly sends users to Beginners' Guide/Extra.
If however Talk:Beginners' Guide#Guide restructuring will be implemented as planned, the Beginners' Guide will have a slightly different installation procedure than this guide, unless this one is updated too.
-- Kynikos (talk) 14:08, 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 a kernel update was involved. --DSpider (talk) 14:41, 24 September 2012 (UTC)
The link to Post-Installation was the last step of the guide, so that's the line I've replaced with the instructions from Post-Installation.
About rebooting in case of a kernel upgrade, I don't think it's necessary to state that since this guide is aimed at experienced users.
In any case, any reordering or modification of the various steps should better be approved by a Developer, and probably the forum or the mailing lists are better places than this talk page to involve them in such discussions.
-- Kynikos (talk) 14:59, 24 September 2012 (UTC)
Yeah, but at this point, you were instructed to reboot. In order to edit pacman.conf, you need to mount the root partition. And to update your system, you need to chroot into it. It would be better if "Unmount leftovers" was renamed "Unmount leftovers and reboot", and added at the end (before the suggestion to read the instructions from Extra). --DSpider (talk) 15:07, 24 September 2012 (UTC)
You are still instructed to reboot, aren't you? The "Unmount leftovers" section currently tells you to "reboot and then login into the new system with the root account". In the "new system", the correct partition is already mounted at /.
Whether or not configuring pacman, updating the system and adding a user would be better done in the chroot before rebooting, it's something that should be discussed with a Developer. I too think that it would make more sense, requiring one less reboot in case of a kernel upgrade.
-- Kynikos (talk) 15:18, 24 September 2012 (UTC)
Renaming "Unmount leftovers" to "Unmount leftovers and reboot" is safe anyway, so I've done that. -- Kynikos (talk) 15:37, 24 September 2012 (UTC)
@DSpider: you're quite active on the forum, why don't you propose your idea there? I think it would be interesting to discuss it. -- Kynikos (talk) 14:11, 25 September 2012 (UTC)
Ok, after reading this I realize that maybe I haven't been clear enough, so I'll try to explain everything more thoroughly.
  1. The current procedure makes you configure the system in the chroot environment from the live system.
  2. Then, still in the live system, it asks you to exit the chroot, unmount the partitions for the new system, reboot and login into the new system. Now, I refuse to write more explicitly in the guide that you should boot into the new system, and not again in the live system, in order to login into the new system.
  3. Since you are now into the new system (not the live system), the root partition is mounted at /, not at /mnt/, so you should be able to configure pacman, update the system and add a user wihtout chrooting. Now, if you've tested the procedure and really noticed that for some obscure-to-me reason you still need to chroot to /mnt in order to do those operations, please ask for clarifications in the forum because I wouldn't be able to answer any more.
Last thing, and I think this is the 3rd or 4th time I write it, I agree with you that configuring pacman etc. could easily be done in the chroot environment at step 1, but you should propose that change in the forum first, since it would be a change in the official installation procedure and I won't take responsibility for that.
I think this is the best I can do here, the next step to explain all this could be making a movie or a five-act play, but I hope it's not necessary :)
-- Kynikos (talk) 05:56, 30 September 2012 (UTC)

Modification to the "Generate an fstab" line

Add a link to the genfstab source in the "Generate an fstab" line. Why? Because if there were ever a time when you'd want to look at what the script is doing, this would be it. And yes, advanced users can find it themselves, but why force them to?

  • Generate an fstab with the genfstab script (if you prefer to use UUIDs or labels, add the -U or -L option, respectively):


I remember that a link to pacstrap's source was removed from the Beginners' Guide because allegedly people were trying to download and run it directly: [3], [4]. Linking to genfstab would go against that precedent... Besides, if you want to inspect genfstab's source from the live system, isn't it much easier to do cat $(which genfstab)? -- Kynikos (talk) 13:50, 28 January 2014 (UTC)


As I mentioned on Talk:Beginners' Guide#Firewall, I think it'd be worthwhile to mention installing/configuring a firewall here along with links to pages like iptables, shorewall, and ufw. --Sudokode (talk) 02:26, 14 January 2015 (UTC)