Difference between revisions of "Talk:Installation guide"

From ArchWiki
Jump to: navigation, search
(Remove closed discussions.)
(Modification to the "Generate an fstab" line: new section)
Line 138: Line 138:
 
--[[User:Ernstkm|Ernstkm]] ([[User talk:Ernstkm|talk]]) 21:50, 4 January 2014 (UTC)
 
--[[User:Ernstkm|Ernstkm]] ([[User talk:Ernstkm|talk]]) 21:50, 4 January 2014 (UTC)
 
: This page is not for first time Arch users. They should read [[Beginner's Guide]] instead.--[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:29, 12 January 2014 (UTC)
 
: This page is not for first time Arch users. They should read [[Beginner's Guide]] instead.--[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:29, 12 January 2014 (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 [https://projects.archlinux.org/arch-install-scripts.git/tree/genfstab.in genfstab] script (if you prefer to use UUIDs or labels, add the {{ic|-U}} or {{ic|-L}} option, respectively):

Revision as of 02:33, 27 January 2014

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 there is something to discuss which should also affect the Beginner's 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.

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 archlinux.org 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 192.168.1.2/24 dev eth0
# ip route add default via 192.168.1.1
# echo "nameserver 8.8.8.8" >> /etc/resolv.conf

--MajorTom

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

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)

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.
https://mailman.archlinux.org/pipermail/arch-releng/2012-July/002708.html --Bluewind (talk) 09:10, 1 August 2012 (UTC)

This really need to be included on tutorial before pacstrap. Otherwise it will not work. Michelboaventura (talk) 16:49, 20 September 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)

Mounting the Swap partition.

Just a note to clarify the swap partition is NOT mounted. You will get an error message if you try.

Turning on the partition with swapon command will have the desired effect of having it activated before you add it to /etc/fstab. --CaptainK (talk) 07:56, 12 June 2013 (UTC)

Hardware compatibility List

The Installation Guide should refer to the Hardware compatibility List at https://wiki.archlinux.org/index.php/HCL in case specific kernel parameters are needed for the mainboard. --Qqqqqqqqq9 (talk) 09:32, 1 August 2013 (UTC)

-1. The info in HCL is out of date so it should not be linked. -- Fengchao (talk) 13:13, 3 August 2013 (UTC)
Close. --Fengchao (talk) 09:32, 12 January 2014 (UTC)

base is redundant in pacstrap command

pacstrap /mnt

works just fine. base is installed by default. KISS, right? I'd do it myself, except it seems regular users don't have permission to edit this page.

Ewtoombs (talk) 22:54, 10 September 2013 (UTC)

Clarify that vconsole.conf must be created

Example: "Add console keymap and font preferences in /etc/vconsole.conf. This file must be created by you."

Please read #Read this first before add new suggestion, first point... Lahwaacz (talk) 20:46, 5 October 2013 (UTC)

genfstab, add -U for uuid

see heading

arch-install-scripts

The page is frozen, could someone edit the section #Install_the_base_system to say that pacstrap is available by installing the arch-install-scripts package? Spent countless hours trying to figure out how to use pacstrap until someone told me this. You might want the pacstrap link in that section to point to the package https://www.archlinux.org/packages/extra/any/arch-install-scripts/ instead of the git! I was trying to install to a new partition, from an existing archlinux install. Thanks Bjka (talk) 04:46, 10 December 2013 (UTC)

See Install from Existing Linux, it provides (or at least it should) all necessary information. -- Lahwaacz (talk) 07:18, 10 December 2013 (UTC)
Category:Getting and installing Arch is linked from the introduction, it was easy to find Install from Existing Linux there. This article covers a standard installation from the live system, where the arch-install-scripts are already available, I've made that clearer in the intro now. Linking to a package before being able to install any could lead to confusion for other users instead, so I'd discard the idea. -- Kynikos (talk) 05:29, 11 December 2013 (UTC)

The section "Install and configure a boot loader" needs improvement

I recommend this one sentence addition:

You may need to install the appropriate bootloader package from the repository using pacman (e.g., pacman -S grub).


The installation guide makes no other other mention of using pacman (specifically) to install packages until near the bottom. You need to know about pacman before you can complete the install. Let's say you're not a beginner with Linux or the command line, but you're a first-time Arch user. That's bound to be confusing.

If you went over to File Systems and decided to create a root btrfs bartition, you'd run into the same problem when it came time to create the initramfs, because you'd be missing btrfs-progs, so maybe a Tip or Note farther up in the guide is in order.

--Ernstkm (talk) 21:50, 4 January 2014 (UTC)

This page is not for first time Arch users. They should read Beginner's Guide instead.--Fengchao (talk) 09:29, 12 January 2014 (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):