Talk:Installation guide

From ArchWiki

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].
  • Due to the wide variety of available boot loaders, the installation guide refers to Arch_boot_process#Boot_loader instead of making a specific recommendation for the installed system. See [6], [7], [8], [9], [10] for some past discussions on this topic.
  • While Category:Installation process lists additional installation methods (e.g. archinstall or systemd-firstboot), the installation guide does not reference them due to their specific nature. Install_Arch_Linux_with_accessibility_options is an exception. See [11] for past discussion on this topic.

-- The ArchWiki Administrators 22:17, 2 September 2016 (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: [12]. 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)
Apparently since last year the translation has been halved in size, but its scope is still much larger than the Install guide (or even the old Beginners' guide). -- Alad (talk) 09:42, 9 May 2021 (UTC)

HiDPI on the console

With an ever increasing number of HiDPI displays, including at the begging of the article a section about adjusting the scaling factor or changing the font can be helpful, see HiDPI#Linux_console. Goetzc (talk) 02:21, 8 August 2019 (UTC)

It could be added as an example for setfont in Installation_guide#Set_the_keyboard_layout. The issue I have is that HiDPI#Linux_console mentions that tty2-6 may be unusable, while the Installation guide specifically instructs to change ttys as required in Installation_guide#Boot_the_live_environment. -- Alad (talk) 13:07, 7 September 2019 (UTC)
May be as an example for the line "See README.bootparams for a list of boot parameters" Installation_guide#Boot_the_live_environment, it could be specified to hit e button to edit the boot entry and add the following parameters to the boot line, like video=1920x1080 if you have HiDPI display. -- Xzorg6 (talk) 22:41, 15 December 2019 (UTC)
video= will just change the resolution. To get a bigger font on the console, you need CONFIG_FONT_TER16x32=y in the kernel config and fbcon=font:TER16x32 in the kernel command line. Since the official kernels don't enable CONFIG_FONT_TER16x32, someone will need to open a bug report asking for it. After that, the instructions for setting the fbcon=font:TER16x32 kernel parameter could be added to the wiki. -- nl6720 (talk) 06:52, 16 December 2019 (UTC)
linux 5.5.6.arch1-1 (currently in testing) has CONFIG_FONT_TER16x32=y (FS#64861). If if gets move to core before March, then the March iso will have it. It's probably a good idea to start drafting a tip to place in Installation guide#Boot the live environment. -- nl6720 (talk) 11:12, 26 February 2020 (UTC)
And just after I wrote this, the package was moved to core. -- nl6720 (talk) 11:27, 26 February 2020 (UTC)
I'm seeing multiple claims[13][14][15] that people with HiDPI screens are getting the TER16x32 font. I was not aware that the kernel chooses a font depending on screen size. Can anyone confirm that this really is the case? If it really works that way and unless FS#65680 messes this up, then there's nothing to add to the Installation guide about this topic. -- nl6720 (talk) 06:02, 11 March 2020 (UTC)
As per the decision to use ter16x32 is not based on screen size but only resolution.So even though a 1080p screen may be hidpi it does not use ter16x32 M.Srikanth (talk) 10:17, 11 May 2020 (UTC)
At least that part is now clear, thanks. The first step should be to get HiDPI#Linux console up to date. After that, as I've said before, a tip for the installation guide can be drafted. -- nl6720 (talk) 11:04, 11 May 2020 (UTC)
I fixed the page and removed the template M.Srikanth (talk) 12:25, 11 May 2020 (UTC)

First mention of /mnt in example partition layout

/mnt is mentioned at mount point in Installation_guide#Partition_the_disks, while /mnt is made explicit two sections later in Installation_guide#Mount_the_file_systems. As I recall it, this was changed because some users blindly copy pasted commands and mounted /boot on the live system, instead of /mnt/boot. Some options:

  • Introduce another column describing the mount point on the installed system.
  • Actually explain /mnt early.
  • Revert the "mount point" to not include /mnt.

-- Alad (talk) 13:03, 7 September 2019 (UTC)

I don't understand what's the actual problem here... -- Lahwaacz (talk) 09:36, 8 September 2019 (UTC)
From what I read on #archlinux-wiki, this comes from where the user was confused by the lack of root mountpoint (i.e. /mnt vs /). A question could be raised, if we should concern ourselves with users who have strong opinions about the wiki content yet can't be bothered to propose improvements in the talk pages...
About Alad's proposed options: I disagree with the first option, I think it will just complicate things even further. I support the third option and maybe adjusting the column header like in Special:Diff/581800.
I'd actually would like to go even further and change the commands run from outside chroot to be visually distinct, e.g.:
root@archiso # mount /dev/sdX1 /mnt
I think it would better solve the underlying issue.
-- nl6720 (talk) 15:26, 8 September 2019 (UTC)
I'm not overly fond of the longer column name. For the last proposed option, I may agree if this is formalized in Help:Style, so that it is not specfic to the Installation guide. -- Alad (talk) 11:20, 10 September 2019 (UTC)
Adding it Help:Style was my intention, since other articles, too, will need to use that style for some commands. I'm thinking of creating a template for it: Special:Permalink/581945. -- nl6720 (talk) 10:19, 11 September 2019 (UTC)
Sounds good to me, I'd just prefer the regular (non-bold) font for the prompt as above. -- Alad (talk) 21:54, 13 September 2019 (UTC)
Special:Permalink/582327. Are there any other opinions about creating such a template? Or should I take this discussion to Help talk:Template per Help:Template#Creation? -- nl6720 (talk) 18:31, 14 September 2019 (UTC)
  1. How are you going to call the template? This template would probably add to the Help:Template#Code formatting templates series, should it be named in a consistent fashion?
  2. Should this template support custom prompts, and if so, should it be called "pc" (from "(custom) prompted" code)?
  3. I don't like the red color too much, if bold is not an option maybe we can go green|purple|blue, something that recalls less a warning of some kind? Or can we just leave it with the default font color? Or a slightly fainter black?
  4. I haven't looked well into it, but maybe we can instead add an optional argument to Template:bc and Template:hc that prefixes a custom (colored) prompt? I wouldn't see a problem with repeating "root@archiso #" in every instance, or we may derive the new template from those two at that point.
  5. The template should probably be derived from Template:bc in any case, for simpler code, see User:Kynikos/Template:Sandbox2.
-- Kynikos (talk) 17:36, 16 September 2019 (UTC)
  1. Initially I was going to call it Template:Archiso since it would be Archiso-specific, but I'm starting to think that creating a more general-purpose template would be better. It could then be used in PostgreSQL and the [postgres]$ convention would get formalized in Help:Style. Now the issue is the [user@peer-a]# in Template:hc used in WireGuard. I'd rather not create two new templates, but I'm having trouble getting Template:Sandbox to work :(
  2. I like your "Template:pc" suggestion.
  3. Be glad I didn't post my first draft that was slightly more colorful. From your offered colors, I'd choose purple.
  4. I'd rather not mess with the established templates just for this change, so I'd prefer creating a new template.
  5. I didn't even think about using Template:bc. Is it a good idea to do that? The new template might need to be updated if Template:bc is ever changed in an incompatible way.
-- nl6720 (talk) 07:33, 17 September 2019 (UTC)
Yeah, after viewing your attempts and looking into it myself, I think modifying bc/hc is out of discussion, it would add too much code/style for so little use.
Thinking about this again one day after, I feel I'm realizing that my concerns in general may descend from the fact that we're going to create a template to represent (block) code, even though we already have 2 which basically do the same thing, including allowing to include a prompt; the only addition of this "Archiso" or "pc" template would be the formatting around the prompt, so why not keep it simple (I know, "simplicity" is often subjective and controversial) and instead either make a Template:Archiso to be used like {{bc|{{Archiso}} mount /dev/sdX1 /mnt}} or Template:ps (or Template:PS) to be used like {{hc|{{ps|root@archiso #}} mount /dev/sdX1 /mnt}}? They also work with Template:hc and space-prefixed code blocks!
Putting the choice of color aside, if the above idea of a standalone prompt template isn't welcome, I think my second choice would be to make two Template:pbc and Template:phc that work like {{pbc|$|ls}} and {{phc|$|ls|...}}, with the style rule to use them only in case of complex prompts. I'd still derive them from bc/hc to inherit any changes that we'd decide to make to them, and avoid repeating that ugly <pre> hack even more.
Otherwise I give up and accept the Template:Archiso that works like {{Archiso|mount /dev/sdX1 /mnt}}, in the hope that one day we won't need an analogous "hc" version.
-- Kynikos (talk) 14:24, 17 September 2019 (UTC)
I can't say I really like the idea of {{bc|{{Archiso}} mount /dev/sdX1 /mnt}} or {{hc|{{ps|root@archiso #}} mount /dev/sdX1 /mnt}}. I'd prefer creating Template:pbc and Template:phc.
I still don't get what's wrong with Template:Sandbox. It should just work:
prompt # command
-- nl6720 (talk) 04:43, 18 September 2019 (UTC)
FWIW (and a bit of fun) I've fixed Template:Sandbox, although I'm not sure if we really need that level of automation ^^ I stick to my position above, is there a third (or more) opinion? -- Kynikos (talk) 15:48, 18 September 2019 (UTC)
I think you like the #800080 shade of purple, right? ;-) Lahwaacz (talk) 11:39, 21 September 2019 (UTC)
Yes, I do like that one :D but I think it would be too bright for this template. -- nl6720 (talk) 11:52, 21 September 2019 (UTC)
Any news on this one? If not, I haven't seen this kind of issue or confusion occur since. -- Alad (talk) 09:37, 31 October 2021 (UTC)
I don't think I want to create such a template anymore, since it would require updating other installation related pages. To go back to your originally proposed options, I'm for explaining /mnt early. -- nl6720 (talk) 09:42, 4 November 2021 (UTC)

Buggy graphics driver

Can there be a hint that nomodeset parameter could be used if the graphics driver is buggy (I've heard nouveau may be buggy sometimes) M.Srikanth (talk) 04:47, 12 May 2020 (UTC)

I would expect this to be mentioned in General_troubleshooting... -- Alad (talk) 09:43, 31 October 2021 (UTC)

GitLab blobs in Lynx

Links to files (blobs) on are not readable in Lynx (or any other console web browser); see

Should the Installation guide link to raw files instead?

-- nl6720 (talk) 12:29, 4 August 2020 (UTC)

Maybe you could ask svenstaro to add it to -- Lahwaacz (talk) 12:36, 4 August 2020 (UTC)
It has been filed under nice to have. -- nl6720 (talk) 17:19, 4 August 2020 (UTC)
Instead of using raw links we should perhaps consider if we need links to gitlab at all. The guide has:
Notice how all but one of these share the common path archiso/-/blob/master/configs/releng. Unless this level of specificity is really required, we could link to this path "for an overview of configuration files shipped with archiso" instead. -- Alad (talk) 09:35, 31 October 2021 (UTC)
I'd prefer simply removing some of the links.
-- nl6720 (talk) 09:30, 4 November 2021 (UTC)
Alright, I've removed those links. (Special:Diff/700696, Special:Diff/700693) -- Alad (talk) 11:39, 4 November 2021 (UTC)
Now that mirrors provide a symlink to the latest ISO version, it's possible to link to pkglist.x86_64.txt. I replaced packages.x86_64 with it. -- nl6720 (talk) 07:31, 21 May 2022 (UTC)
Is Lynx (un)readability such a big problem in this case? People using Lynx from the archiso can open up the relevant file in the live system itself... — Lahwaacz (talk) 18:05, 31 October 2021 (UTC)


I skipped steps in the guide so I faced a weird crash in gnome without any explanations. I suggest a note.

Note: Many of them assume that you have your timezone or locales set up. Make sure you have followed all the steps.

Escope (talk) 10:11, 2 April 2021 (UTC)

The reader is supposed to follow all the steps. If we apply that to other pages, the pages need a boatload of notes to make sure the reader did not skip any steps. A common functional system has properly configured locales and timezones.
Since this is GNOME-specific however I would at most add a section into GNOME/Troubleshooting or even General troubleshooting, but I still think this is out of scope to be honest. Many applications may not work properly when the timezones or locales are not correctly configured.
-- NetSysFire (talk) 15:30, 2 April 2021 (UTC)
The reader is not supposed to follow all the steps in case one doesn't worthy of attention. In my humble opinion, that's why it has huge advantage over the "Next-Next-Finish" approach. Unconfigured locales or timezones are obvious to many people, but my inexperience made me spend some time to sorting out. The other pages are highly deep and clear about the steps and why they are needed, my eyes enjoy such notes, pages are boatloaded already and I like it a lot =D. Thank you for your attention to this little change.
-- Escope (talk) 00:23, 3 April 2021 (UTC)
If you're inexperienced, what makes you think you can judge if a step is necessary or not? You thought you knew better than the people that wrote the guide and found out that you didn't. Not something that needs changed here IMO.
Scimmia (talk) 01:57, 3 April 2021 (UTC)
The ArchWiki should also be about the why-aspect. I am in favor of adding e.g a note about why they are needed and why some applications may crash or behave strangely without properly configured timezones/locales. If you know e.g a nice blog post about this topic, why not add something like this?
Note: Some applications may behave in strange ways or even crash when the timezones and/or locales are not properly configured. See this informative blog post to know why that is.
The note needs obviously some rewording, but something like this would fit in well in my opinion.
-- NetSysFire (talk) 02:02, 3 April 2021 (UTC)
Adding a brief "why" would be ok, but using Template:Note would be too much. I've also always wanted to emphasize the "and" in Installation guide#Localization, since it's easy to miss (even some of the translated installation guides do not mention en_US.UTF-8 UTF-8). --- nl6720 (talk) 08:48, 3 April 2021 (UTC)
People who want to know the "why" can already consult the relevant articles. That said, consistency is lacking: some sections explain in detail why a step should be performed (such as Installation_guide#Verify_signature), whereas Installation_guide#Configure_the_system is mostly a checklist of steps with brief instructions how. The solution isn't obvious: adding notes all over would likely more distract than clarify. -- Alad (talk) 19:41, 14 April 2021 (UTC)
I'm definitely apposed to adding notes, but I don't see why we couldn't add brief "why"s without them. -- nl6720 (talk) 06:55, 15 April 2021 (UTC)

Add link to ALSA firmware in the Install essentials packages section

With sof-firmware gaining more and more traction on newer systems it might be useful to add a link or piece of information that this might be necessary for newer laptops/cards, see Advanced_Linux_Sound_Architecture#ALSA_firmware. We currently get pretty much daily reports on the BBS where someone wonders where their sound card has gone. I know this is "technically" included in the "install additional firmware not included in linux-firmware" line, but since this is something that hasn't really been necessary for years this is potentially something not everyone is immediately aware of. V1del (talk) 17:15, 13 August 2021 (UTC)

Even with a link to Advanced_Linux_Sound_Architecture#ALSA_firmware, it might be confusing that it applies based on the hardware, even when the user wants to use PulseAudio or Pipewire. Is there a better place where audio firmware could be described? — Lahwaacz (talk) 20:00, 13 August 2021 (UTC)
I tried to have some sort of "standardized" snippet on laptop pages when it needs ALSA firmware, but the ArchWiki is not a hardware db and we cannot document all pieces of hardware. Audio is not essential for some users but a few depend on screenreaders, which is crucial to accessibility.
In the end it might not cause harm to install sof-firmware when in doubt.
-- NetSysFire (talk) 01:17, 14 August 2021 (UTC)
I mean if we cover firmware in e.g. Sound system and link to that instead of ALSA, it would seem much more general. — Lahwaacz (talk) 06:19, 14 August 2021 (UTC)
Well for this particular case you can fairly easily identify whether you have a need for sof-firmware with an lsmod | grep snd_sof or a dmesg | grep -i sof, but yes might be helpful to move that somewhere else if we want to ensure to have hardware based separation here. V1del (talk) 12:04, 14 August 2021 (UTC)
I added sof-firmware as an example (and the aforementioned link) so that there's at least something for now. -- nl6720 (talk) 10:20, 25 August 2021 (UTC)

Add a check for "native sector size" before/during partitioning step

Some pages like Solid state drive are nearly impossible to get to from just following the Installation Guide. This is problematic as some recommendations from these pages are only relevant before installation, as it is too late afterwards (notably for setting native sector size as in Solid state drive#Native sector size. I believe there should be a note in the partitioning step, something like modifying this line:


As an alternative, this could be added to Partitioning, but it's already quite big... -- Cvlc (talk) 15:47, 29 August 2021 (UTC)

Linking both Improving_performance#Partitioning (which needs improvements) and Solid state drive seems excessive. Also, it's unclear if the improvement is tangible enough to make users work through yet another wiki article for their basic setup. -- Alad (talk) 09:28, 31 October 2021 (UTC)
An alternative could be to add :
Tip: Check that your disk reports the correct sector size
at the beginning of partitioning. It's an important optimization step and currently not addressed. On a brand new nvme SSD, strictly following the wiki, I ended up with a wrongly set up LUKS volume because the drive reports 512 byte sectors as the active option, and I only found out after installing.
-- Cvlc (talk) 16:15, 23 November 2021 (UTC)
Seeing as the "native sector size" is the only issue that can't be simply fixed after the fact (unlike e.g. TRIM), it should be fine to link it (after Talk:Advanced Format#Rewrite Advanced Format to a new Sector Sizes page is done). As for linking to Solid state drive in general, IMHO there's no need. It's already linked from General recommendations#Solid state drives. -- nl6720 (talk) 09:53, 25 November 2021 (UTC)
Agreed, the sector size issue was the one that really bothered me. I corrected the title.
-- Cvlc (talk) 11:05, 25 November 2021 (UTC)
Now that Talk:Advanced Format#Rewrite Advanced Format to a new Sector Sizes page is done, I suggest adding
Tip: Check that your disk reports the correct sector size
before the partitioning step
-- Cvlc (talk) 03:42, 4 December 2021 (UTC)
As I already mentioned, there's a lot of steps involved in that article for unknown gains. Presumably, most people will think it's a requirement (due to the general nature of the article) even when formatted as a tip. Only Advanced_Format#Alignment is straightforward and already handled by fdisk. -- Alad (talk) 09:51, 9 January 2022 (UTC)
It's true that it's not a very simple article, but it's actually not that bad since people will skip to either HDDs or SSDs sections which are much more to the point. What do you think would be a better way to address this? formatting the disk to the correct sector size cannot be done at a later point in time. Again, all of this stems from the fact that it happened to me, and it's going to happen to anyone with a similar setup (most hardware with recent SSDs). What if I try simplifying the Advanced format article further ? --Cvlc (talk) 20:43, 9 January 2022 (UTC)
Perhaps something like "Tip: adjusting the storage device's sector size before partitioning it might be beneficial for performance." Neven (talk) 00:20, 6 May 2022 (UTC)
I'd omit the "for performance" part, since such claims would need references. And since not every drive can change its logical sector size, IMHO it would be better to explicitly mention to who the tip applies to. From what I understand, that would be a large part of NVMe drives and some "enterprise" SATA HDDs. Despite what Advanced Format says, I couldn't find anything about SATA SSDs that support changing their sector size.
-- nl6720 (talk) 13:18, 6 May 2022 (UTC)

Remove parted

Due to parted not aligning the partition size (and with no patch in sight) which prevents using 4096 byte sectors with dm-crypt/LUKS unless explicitly planned before, I'd like to remove the "parted" link from Installation guide#Partition the disks. An alternative would be to change all examples in Parted to not use percentages and warn against using them. -- nl6720 (talk) 07:21, 7 April 2022 (UTC)

I prefer to change the examples in Parted. Just removing the link from installation guide won't stop people from using the tool. -- Alad (talk) 10:52, 7 April 2022 (UTC)

Note on Network Setup

One of the most common installation issues that comes up on Reddit, Forums, and other discussion areas is not having done any sort of network setup. While the Installation Guide explicitly call out Network Setup as a required step, I suspect people are mistakenly believing the setup steps they did already to establish a connection on the installer will carry over to their installed system.

I propose adding a note such as (example content):

Note: Configuring your network connection above only established your network for the installer. This section will configure the network for your installed Arch system. Failure to do so may leave you without network access after completing installation.

Nalthien (talk) 17:40, 15 May 2022 (UTC)

Such a thing does not warrant a warning since there's nothing dangerous about being offline. It may even be the safest state the system will ever be. -- nl6720 (talk) 10:24, 18 May 2022 (UTC)
I can agree that it doesn't warrant a Warning given the style guide; however, I do think a Note would be appropriate to "highlight information easily overlooked." It's clearly overlooked quite often. Nalthien (talk) 17:36, 20 May 2022 (UTC)
Installation guide#Connect to the internet already explains (or tries to, at least) that the live environment's network setup has nothing to do with the installed system. Perhaps the list items in Installation guide#Install essential packages could be made a little more verbose to explain why someone may want to install those things. -- nl6720 (talk) 10:24, 18 May 2022 (UTC)

Clarify root mount

Without having perused history, I suggest to change Installation guide#Mount the file systems slightly from

Create any remaining mount points (such as /mnt/efi) and mount their corresponding volumes.


After the root volume is mounted, create any remaining mount points (such as /mnt/efi) and mount their corresponding volumes.

an alternative may be to add to the following tip (e.g. "Alternatively, create it using mkdir(1) beforehand, but only after mounting the root volume.")

Reason: lsblk will happily show a /mnt/boot, even if it was mounted too early, potentially messing up pacstrap and genfstab. It will work, if /mnt/boot is mounted twice (once before and after root), but it is simpler to explicitly address mount order.

--Indigo (talk) 17:01, 2 June 2022 (UTC)

As the previous instruction is "Mount the root volume...", this seems pretty redundant. Scimmia (talk) 18:14, 2 June 2022 (UTC)
Frankly, I don't remember how the ISO behaves regarding pkg-cache: Will a repeated pacstrap download updates again? --Indigo (talk) 19:29, 2 June 2022 (UTC)
pacstrap(8) uses the target's package cache by default. If the target was correct, then there will be no re-downloading on repeated runs. -- nl6720 (talk)
Ok, thanks. --Indigo (talk) 19:00, 3 June 2022 (UTC)
I think all the confusion comes from new users not understanding the hierarchical structure. How about something like : "Create any remaining mount points (such as /mnt/efi) and mount their corresponding volumes in a hierarchical order." -- nl6720 (talk) 07:27, 3 June 2022 (UTC)
That's clearer for the rest, yes. I'd make that suggestion "Create any remaining mount points (such as /mnt/efi) and mount the volumes in their corresponding hierarchical order."
Regarding the root mount, I do understand the resentment to deviate from the established and proven form, fine.
This escapes the topic a little, but perhaps a catch-all procedural sentence is what it needs instead. For example, to the third intro paragraph: "This guide is deliberately kept concise and you are advised to follow the instructions in the presented order per section. For more detailed instructions, see the respective ArchWiki article or the various programs' man pages, both linked from this guide.".
--Indigo (talk) 19:00, 3 June 2022 (UTC)
Yes, "their corresponding hierarchical order" sounds a lot better.
I don't think the resistance to change is that bad. :) We could alter the root mount text if there's some consensus about it.
IMHO "deliberately kept concise" gives off a negative connotation. I can't think of any better suggestions at the moment, though.
-- nl6720 (talk) 11:17, 4 June 2022 (UTC)
How about "intentionally concise and you are advised ..."? --Indigo (talk) 15:38, 8 June 2022 (UTC)
That sounds better to me. 👍 -- nl6720 (talk) 05:11, 9 June 2022 (UTC)
Or since "intentionally concise" is not concise, "This guide is kept concise and ..." :) -- Alad (talk) 13:10, 12 June 2022 (UTC)
Ok. To summarise, we'd add:
"This guide is kept concise and you are advised to follow the instructions in the presented order per section." to start the third para intro,
and change corresponding sentence in Installation guide#Mount the file systems to
"Create any remaining mount points (such as /mnt/efi) and mount the volumes in their corresponding hierarchical order."
if no further objections arise.
--Indigo (talk) 16:54, 15 June 2022 (UTC)
A month has passed with no objections. I think you can update the page now :) -- nl6720 (talk) 13:56, 15 July 2022 (UTC)

Partitioning tools

Is there any reason gdisk is not listed as an option? If we include parted, despite problems with alignment, I don't see why gdisk is excluded. The wiki page for fdisk actually suggests gdisk as an alternative. I'm probably not the only one who learnt to use gdisk for GPT and it is nice to use a familiar tool if there's no reason not to. But I don't want to add it if it's omitted for a reason. --cfr (talk) 01:29, 20 August 2022 (UTC)

fdisk linking to gdisk is the result of a previous discussion about this.
Personally, I agree that Installation guide#Partition the disks should mention gdisk. My suggestion would be: "Use fdisk, parted or gdisk (GPT only) to modify partition tables".
-- nl6720 (talk) 10:16, 20 August 2022 (UTC)
By the same argument, we should then mention cfdisk, cgdisk and any other partition tools. As such I'd suggest the following instead: "Use a partitioning tool like fdisk or parted to modify partition tables". -- Alad (talk) 13:32, 24 August 2022 (UTC)
Your suggestion is better than the current text at least. -- nl6720 (talk) 08:44, 25 August 2022 (UTC)
In the end the situation is quite similar to the one for boot loaders and network managers. I wouldn't mind listing more alternatives (or even tables) in the installation guide, but then the reasoning has to be applied equally to other sections. -- Alad (talk) 15:08, 25 August 2022 (UTC)
I hope it's nothing like this sorry excuse for a table.
The thing with partitioning tools, compared to e.g. network managers, is that there are not that many of them. There's basically just fdisk, gdisk and parted. fdisk & gdisk additionally have scriptable and text user interfaces. And there are GUI ones based on parted.
I'd say let's go with your suggested text for now. We'll get to the greater goal eventually :D
-- nl6720 (talk) 15:22, 25 August 2022 (UTC)
The table in Partitioning#Partitioning tools got better, so IMHO it should be fine to link to it now. -- nl6720 (talk) 16:04, 28 August 2022 (UTC)
The "old" beginners' guide had a similar table included: User:Alad/Beginners'_guide#Partition_the_devices. Considering the small size, it could make sense to include the one from Partitioning#Partitioning tools in the installation guide directly. The downside is the GUI wrappers don't apply to the live environment. -- Alad (talk) 16:36, 28 August 2022 (UTC)

Use pacstrap -K

For 🕰️ reasons, once a monthly ISO with arch-install-scripts 27 (not yet released) is out, we should update all pacstrap commands to use the new -K option.

Since the Installation guide#Update the system clock step is before Installation guide#Install essential packages, this would ensure that the time is correct when pacman-key --init runs thus partially preventing the aforementioned issue.

-- nl6720 (talk) 13:24, 29 August 2022 (UTC)

The UTC+X issue was fixed in a different way[16], but I still added the -K option. It should be considered more secure for the Install Arch Linux from existing Linux method and it's simpler if the command is consistent between all articles. -- nl6720 (talk) 12:20, 3 October 2022 (UTC)

ESP mount point

The installation guide uses

# mount --mkdir /dev/efi_system_partition /mnt/boot

Shouldn't it point to EFI system partition#Typical mount points instead ? --Cvlc (talk) 15:36, 13 September 2022 (UTC)

I would like the discussion I started at Talk:EFI system partition#Recommendation of /efi over /boot to be resolved first. In its present state, the linked page would not be able to help a new Arch user for example. --Erus Iluvatar (talk) 19:16, 13 September 2022 (UTC)

Simply put, using (/mnt)/boot will work with all boot loaders. Whether any other mount point can be used will depend on the boot loader/manager capabilities. See past related discussions: Special:Permalink/706608#Reducing /mnt/efi to a footnote, Special:Permalink/693979#Consider warning users about the additional steps required when selecting a partition other than /boot as their ESP. It's simpler to have it this way. -- nl6720 (talk) 09:14, 15 September 2022 (UTC)
EFI system partition#Typical mount points got shaped up, but we already link to it in Installation guide#Example layouts, can we consider this closed? --Erus Iluvatar (talk) 18:45, 24 September 2022 (UTC)
Alright, maybe we can reopen this at a later time if it ever gets easier to perform a clean install with Unified kernel images. Apart from that, it's probably better to leave it as it is.
-- Cvlc (talk) 00:25, 30 September 2022 (UTC)