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 , ,  and  for some past discussions about this issue.
localectl list-keymapsdoes not work due to bug FS#46725. For the chosen replacement command, see .
localhostmust 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)
- 1 Read this first before adding new suggestions
- 2 Link to the German version
- 3 Network configuration
- 4 Why should a static IP be preferred over 127.0.1.1 in /etc/hosts?
- 5 Network Configuration -- WiFi discussion
- 6 fstab
- 7 Wording in example layout table and size of EFI partition
- 8 Boot loader installation
- 9 Confusing partition numbers
Example layouts for partitions
Link to the German version
dhcpcd for installed environment
How about we add a sentence to Installation_guide#Network_configuration describing how to restore use of dhcpcd as done on the installation medium? That way if the connection already worked on installation people only need a brief look at dhcpcd. -- Alad (talk) 15:48, 27 May 2018 (UTC)
- I think that would just hide the possibility of choice from users. Maybe just say that dhcpcd is not enabled on the installed system without recommending anything. -- Lahwaacz (talk) 17:34, 27 May 2018 (UTC)
once chrooted, one has to configure again
One chrooted, configuration file edited in the previous steps, will have to be redone in the chrooted environment (/etc/systemd/network/ files). This is the same for ntp configuration (/etc/systemd/timesyncd.conf).
This should be worth noting.
- The guide does not say to edit anything under
/etc/systemd/in the first place, so there is nothing to be redone. Furthermore, Installation guide#Network configuration says to "Complete the network configuration for the newly installed environment." -- Lahwaacz (talk) 17:27, 17 May 2019 (UTC)
Why should a static IP be preferred over 127.0.1.1 in /etc/hosts?
"If the system has a permanent IP address, it should be used instead of 127.0.1.1."
- In Network_configuration#Local hostname resolution: "For a system with a permanent IP address, that permanent IP address should be used instead of 127.0.1.1." -- Lahwaacz (talk) 06:48, 22 May 2018 (UTC)
Network Configuration -- WiFi discussion
I'm starting a new thread seeing as the last one took a different direction and never really got resolved.
As it stands, the current instructions for the installation guide make it challenging for users who need to connect to the internet via a Wireless connection rather than wired. The Installation_guide#Connect_to_the_Internet section essentially assumes the users are using a wired connection, and to test it with a ping. Otherwise, they are directed to the Network_configuration page. Unfortunately, that page does not provide clear instructions for new users (or even those who just want to do a quick connection) to establish a connection via wireless. Equally so, should users find their way to the Wireless_network_configuration page, there is some digging to do there in order to find instructions to setup a connection. These are currently using the iw command, which may prove to be challenging to some. I see a few different possible solutions to improve the user experience:
- Add explicit instructions to the installation guide
- This is not ideal, as it adds another place to maintain likely duplicate information
- Add a reference to the Wireless_network_configuration page
- This is better, though the page would likely need a new section, or some tweaking to allow users to more easily find the information they need to get setup
- Add new/better instructions to the Network_configuration page
- This may also prove to be tricky, seeing as that page is already fairly monolithic, and focuses mostly on wired connections
One other consideration (of which I also don't see any progress) is the discussions revolving around moving and breaking down the Network Configuration guides, to separate Wired and Wireless content. With this move I could see such instructions being provided there. In any case, the guide should provide instructions that are:
- Easy to follow, particularly for new users
- Puts no emphasis on persisting configurations, as this is not applicable during the install phase
- Offers options (choice is King)
- The Wireless network configuration link was removed because it cannot be used independently of Network configuration. I propose the following:
- Implement Talk:Network configuration#Moving Ethernet-specific sections to Wired subpage. Network configuration currently isn't straightforward. The actual setup instructions are hidden in the Network management section and it's confusing that wireless has a subpage but wired and medium-agnostic configuration are mixed together. See my demo.
Have the Connect to the Internet section only link Network configuration and move the dhcpcd udev rule note there.
- Move Wireless network configuration to Network configuration/Wireless and move its iw section to a dedicated article because since recently we also have iwd.
- The result should be more user-friendly without duplicating content.
- --Larivact (talk) 07:13, 27 August 2018 (UTC)
- As for your demo, note that in Talk:Network_configuration#Ongoing_rewrite, Alad said: "ping is one of the very first commands a new user has to run on installation to verify the availability of an internet connection". So unless you intend to direct users from the installation guide directly to the Network configuration#Troubleshooting section, there is still some more thinking to be done... -- Lahwaacz (talk) 07:21, 28 August 2018 (UTC)
- Well then let's keep Connect to the Internet and revise it:
# ping archlinux.org
If the ping fails see Network configuration#Troubleshooting. If you want to use Wi-Fi or a static IP address, stop the dhcpcd service with
systemctl stop dhcpcd@interface where the
interface name can be tab-completed and proceed with Network configuration.
The section about generating the fstab with genfstab mentions -U and -L options but not the possibility to use GPT identifiers PARTUUID and PARTLABEL with the '-t' option. Those are described in Persistent block device naming and are a better choice for some users. genfstab itself doesn't explicitly list the GPT options either so IMHO it would be helpful to add this info here.
- In that case you should open a bug / file a patch such that
genfstabdoes list these options. The wiki shouldn't make up for missing basic documentation in distribution tools. -- Alad (talk) 17:49, 13 March 2019 (UTC)
Wording in example layout table and size of EFI partition
Wording in example layout table
even if many users will understand remainder of the device as what is left after size of /dev/sdx1 and /dev/sdx3 are subtsructed from the size of the device, I think the order of the table might be confusing for some. Some people might set /dev/sdx2 to the size of the device minus size of /dev/sdx1, and then stumbled at where from 512 MiB, or larger, are to be found for /dev/sdx3. Either suggest the swap space as /dev/sdx2 and / as /dev/sdx3, or better explain the meaning of the remainder of the device for sdx2. Regid (talk) 14:05, 29 December 2018 (UTC)
- Using /dev/sdx2 for swap is questionable, it doesn't emphasize that swap is optional nor is it consistent with other articles like dm-crypt/Encrypting an entire system. If you have some better explanation for "remainder of the device" feel free to propose it. -- Alad (talk) 08:55, 30 December 2018 (UTC)
- I was trying to say that a user that patitions his HD by following the table might do the following: look at first row in the table, and creates the EFI partition. Than continue with the 2nd row. So he creates a partition at the remainder of his HD. Now he comes to the 3rd row: where will he get 512 MiB, or larger? As for dm-crypt/Encrypting an entire system, I might be wrong thinking that each partition is considered a separate device, so it doesn't matter if the swap space is before, or after, the / partition. Regid (talk) 12:41, 30 December 2018 (UTC)
Boot loader installation
Installation guide#Boot loader doesn't say to install a boot loader, it only refers to a list of them. How about adding something like "Choose and install at least one boot loader."? -- nl6720 (talk) 19:46, 14 March 2019 (UTC)
- Might not be the most common scenario, but it's possible to use one boot loader for BIOS booting and another for UEFI booting. E.g. rEFInd for UEFI booting + Syslinux for BIOS booting. If that use case is too uncommon to be mentioned then just add "Choose and install a boot loader.". -- nl6720 (talk) 21:31, 14 March 2019 (UTC)
Boot loader options
Is it worth saying that without
init=/lib/systemd/systemd kernel parameter?
I got a bad surprise when I uninstalled the thing. – flying sheep 08:05, 18 April 2019 (UTC)
- That is not something that belongs in the Installation guide. The
init=parameter is documented in Kernel parameters#Parameter list and its description hints at the consequences of uninstalling .
- What made you decide to uninstall nl6720 (talk) 10:37, 18 April 2019 (UTC) ? --
- I decided I didn’t need the aliases it provides. Little did I know that one of them is Linux’ defaults.
- I think it’s a bit hidden there and there should be some way to discover this in the wiki while installing – flying sheep 16:58, 22 April 2019 (UTC)
- bootctl is systemd-boot's installation command. The wiki should not give preference to a specific boot loader. -- nl6720 (talk) 15:13, 16 May 2019 (UTC)
Confusing partition numbers
The partition numbers on this page are confusing. The table calls the root partition /dev/sdX2, while the text below calls it /dev/sdX1. It should be matched for consistency. Sabinscabin (talk) 20:29, 13 April 2019 (UTC)
# ln -sf /usr/share/zoneinfo/x/y /etc/localtime
# ln -sfr /usr/share/zoneinfo/x/y /etc/localtime
Keeping relative links isn't better?
Example layouts for partitions
Why suggest only 512MB of Linux SWAP when it's recommended to use double the RAM?