Talk:Installation guide

From ArchWiki
Jump to: navigation, search

Read this first before adding new suggestions

  • systemd tools such as hostnamectl, timedatectl and localectl do not work in the installation chroot environment, so please do not propose to use them in the guide unless you can prove that they have been made to work also in that case. See [1], [2], [3] and [4] for some past discussions about this issue.
  • localectl list-keymaps does not work due to bug FS#46725. For the chosen replacement command, see [5].
  • localhost must be set explicitely in /etc/hosts, as it is otherwise resolved over the network. See FS#56684.

-- The ArchWiki Administrators 22:17, 2 September 2016 (UTC)

Pinging doesn't respond to pings, so pinging it is not a great test of network connectivity.

The guide should have you ping an subdomain that does respond to pings - if there is one - or something like --Parenthephobia (talk) 12:20, 1 April 2018 (UTC)

The guide says to ping which responds just fine. Closing. -- Lahwaacz (talk) 12:23, 1 April 2018 (UTC)

pacman-key --populate

[Moved from Talk:Beginners' guide. -- Alad (talk) 20:38, 12 July 2016 (UTC)]

Reference: I tried to install Archlinux on my new computer and got stuck. Only using the pacman-key --populate archlinux helped me. I think I am not the only one having this problem. But why did you undo it? —This unsigned comment is by Sandstorm (talk) 20:38, 12 December 2015‎. Please sign your posts with ~~~~!

This command is already run for the new system (by installation of archlinux-keyring), so running it by hand shouldn't be required for most users. Of course, things can go wrong (how old was the ISO you used to install the system?), but that belongs in Troubleshooting sections of the respective articles, which are linked at the beginning of the guide. -- Alad (talk) 19:52, 12 December 2015 (UTC)
I had downloaded the ISO just yesterday, minutes before the install. Only that command installed the keys. Probably I should open a bug if you can confirm the issue?
Did you have to run pacman-key after, or before pacstrap? And do you recall what the error messages said exactly? (See also FS#31286) -- Alad (talk) 20:15, 12 December 2015 (UTC)
I had to run after pacstrap. As far as I remember, pacstrap stopped after trying to download the keys. The error message was something like shown in this forum post:
Well then, as you suggested, I'd open a bug report. -- Alad (talk) 20:34, 12 December 2015 (UTC)
Done. Could you check if the description is good. I could not find an appropriate category, so I though Packages:Core might be the closest one. --Sandstorm (talk) 20:48, 12 December 2015 (UTC)
Thanks, the description looks OK. If the category e.a is not right, User:Scimmia should fix it. :P -- Alad (talk) 13:59, 13 December 2015 (UTC)
Hmm, looks like it was closed with "Works for me" ... not very enlightening. All I can suggest is to further improve on Pacman/Package signing and related articles, and recheck if they're accessible enough from the Beginners' guide. -- Alad (talk) 21:59, 12 February 2016 (UTC)

Switch to systemd-networkd

Next ISOs may use systemd-networkd instead of dhcpcd, see [6] -- Alad (talk) 10:26, 19 July 2016 (UTC)

Include hint at top of page for install.txt

Inform users that a copy of the installation guide can be found in ~/install.txt on the live CD.

This would be incredibly helpful for users who potentially don't have access to two computers at the same time. —This unsigned comment is by Cheeseypi (talk) 23:33, 13 November 2017‎. Please sign your posts with ~~~~!

install.txt is not a real copy in the sense that all wiki links are missing, and those without two computers can simply switch ttys to elinks as is described in Installation_guide#Pre-installation (throughout the guide, a working internet connection is assumed). -- Alad (talk) 07:57, 14 November 2017 (UTC)

Link to the German version

Instead of de:Arch Install Scripts you could choose de:Anleitung für Einsteiger it means "Beginner's Guid" and is a very detailed artikel for very new arch users and the future experts.

Thank you, done. -- Kynikos (talk) 16:31, 6 February 2018 (UTC)
This was already proposed last year and rejected: [7]. I don't see what has changed since then. If someone adds me as admin to the german wiki or changes the protection settings, I can update de:Arch Install Scripts as required. -- Alad (talk) 18:13, 6 February 2018 (UTC)
I see, I didn't remember that discussion so I've reverted the change, hopefully you'll make it to update the translation, let's leave this open until the problem is solved, otherwise this kind of suggestion will keep appearing recurrently. -- Kynikos (talk) 17:53, 7 February 2018 (UTC)

make a recommendation to install 2 kernels

in very rare cases a kernel upgrade may render the system disfunctional. this is easy avoided by installing the 2 different default verisons of the kernel, e.g. linux(-zen/hardened) and linux-lts. downgrading or fixing a broken kernel is a lot of hassle. should it not be recommended to install 2 kernels if space is no problem? --Soloturn (talk) 18:31, 31 March 2018 (UTC)

As you've mentioned, this is too rare to make a general recommendation out of it. It might even happen that all installed kernels break at the same time... -- Lahwaacz (talk) 18:51, 31 March 2018 (UTC)

Partition the disks: GPT on BIOS system

Suggestion: add a third partition suggestion:

* If using a BIOS system with a GPT scheme using the GRUB boot loader, a BIOS boot partition.

Discovering this requirement when installing a bootloader is a bit too late. -- Lekensteyn (talk) 18:08, 4 April 2018 (UTC)

The BIOS boot partition is required only for GRUB, in which case its installation instructions should be read anyway. -- Lahwaacz (talk) 20:52, 4 April 2018 (UTC)
The only other supported bootloader for GPT on BIOS (according to Category:Boot_loaders) is syslinux which looks more complicated (and also needs a special attribute to be set). What about the new suggestion (a reminder for GRUB users)? (Otherwise, do you have alternative helpful suggestions for GPT on BIOS?) -- Lekensteyn (talk) 14:47, 5 April 2018 (UTC)
There are more options than syslinux and grub. Also, this was already discussed before. -- Lahwaacz (talk) 18:44, 5 April 2018 (UTC)


Currently (archiso 2018-04-01), the hosts file is pretty empty, presumably due to nss-myhostname. Perhaps remove the suggestion of editing it? -- Lekensteyn (talk) 18:08, 4 April 2018 (UTC)

The instructions are there due to the note in Network_configuration#Local_network_hostname_resolution. If there is something new, that page should be updated first. -- Lahwaacz (talk) 20:57, 4 April 2018 (UTC)
I am tempted to erase that whole section. The two "However, clients may still rely on ..., see ..." do not require the hosts file, just that the system resolver provides a valid result (which seems done now via the nss-myhostname module). The change that empties /etc/hosts was, I think that the wiki should adapt to that. -- Lekensteyn (talk)
No. Please read the first section of this talk page. -- Alad (talk) 15:04, 5 April 2018 (UTC)