Difference between revisions of "Talk:Installation guide"

From ArchWiki
Jump to: navigation, search
(pacman-key --init / populate?)
m (Suggestions to update this guide as part of ISO)
Line 142: Line 142:
Set static IP
Set static IP
# ip link set dev eth0 up
  # ip addr add dev eth0
  # ip addr add dev eth0
  # ip route add default via
  # ip route add default via

Revision as of 01:04, 9 August 2012

Page purpose and why it is locked

As Falconindy said:

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. See also discussion about changes to Beginners guide. -- Fengchao (talk) 04:44, 24 July 2012 (UTC)

Maybe this section should be moved to the main article to make it clear. --PMay (talk)
+1 Make the purpose clean and redirect people want to add/read detailed instructions to Beginners' Guide. -- Fengchao (talk) 02:50, 25 July 2012 (UTC)

Leave this wiki entry KISS

If anyone wants to discuss/add sth, then do it on Talk:Beginners'_Guide/Installation as already stated in the first place. An advancded user will find this page less bloated and easier to read, so let's KISS. --Maevius (talk) 14:59, 24 July 2012 (UTC)

Please remove the edit lock.

Can you please remove the edit lock? --PMay (talk) 09:36, 24 July 2012 (UTC)

No. I won't. I'm going to end up repeating myself several times on this page, apparently. This wiki is meant to be a concise checklist of things that need to be done in order to get a running system. I refuse to let it turn into another beginner's guide, covering every single fathomable configuration knob that one could possibly touch. We have an enormous wiki full of this sort of info. There is absolutely nothing to be gained by doing anything but linking to it here, rather than repeating it. I have zero faith that removal of the edit lock will allow the page to remain in a state that I'm comfortable with. Falconindy (talk) 12:50, 24 July 2012 (UTC)

Mounting partitions

You do not mount partitions. Change this to mounting filesystems and possibly add a section about creating filesystems.

Change Install and configure to Install a bootloader

In step 6 should it read Install a bootloader instead of Install and configure? Configuration should be made once in chroot. At least that's the case with syslinux. The command /usr/sbin/syslinux-install_update -iam should be issued from within chroot to succeed. --Maevius (talk) 07:33, 17 July 2012 (UTC)

GRUB2 configuration

I took the liberty and edited the whole page. If someone could write a line or two about grub2 configuration that'd be great. --Maevius (talk) 09:10, 17 July 2012 (UTC)

  • Thanks for your contribution, but the 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. Falconindy (talk) 13:33, 17 July 2012 (UTC)
  • Yeah, I thought about that... What if we moved it in its current state somewhere else and then revert this one as it were before?--Maevius (talk) 18:28, 17 July 2012 (UTC)
  • I'm no expert so when I was installing Arch last night the GRUB2 installation was confusing. I thought I had installed it and that would be it. Took me a little while to get to the GRUB page and find out how to configure it. So, basically, I was thinking it might be good to just put a link, say this one, to the GRUB config section. It would be simple and not affect the KISS of this wiki entry. But I don't think its something that is for the beginner page. --Uhgreen (talk) 14:13, 25 July 2012 (UTC)

need to load GRUB again or not

Just wanted to check, grub is loaded as part of base packages so there is no need to load it again. Simply install syslinux or configure grub. Mr Green 17 July 2012 (UTC)

I don't believe any bootloader is included in base. You have to pick one and install/configure it. --Emiralle (talk) 17:11, 24 July 2012 (UTC)

Configure the bootloader

From the section Configure the bootloader in Configure the system: Shouldn't you edit the syslinux.cfg to point to the right / (root) partition? Or why don't we just put a link to the corresponding section of the syslinux page there? Guelfi (talk) 09:18, 21 July 2012 (UTC)

  • I'd rather get rid of the mentions of configuring separately. It's weird. Why isn't the installation section sufficient? Falconindy (talk) 12:05, 21 July 2012 (UTC)
    • I have edited it as Guelfi Suggested. Here is an example showing that Guelfi is right. --Kaurin (talk) 01:52, 23 July 2012 (UTC)
      • At least we should add "syslinux-install_update -i -a -m -c /mnt" after pacstrap /mnt syslinux because otherwise there will be nothing in the MBR to boot from. After that /boot/syslinux/syslinux.cfg APPEND Line has to be changed to point to the real root partition. By default it points to root=/dev/sda3.--Blackout23 (talk) 12:56, 26 July 2012 (UTC)
        • Also this has to be done before arch-chrooting otherwise MBR installtion will say "/mnt/boot is empty Is /boot mounted?. Even though ls showed me that there is /boot with syslinux installed. --Blackout23 (talk) 13:09, 26 July 2012 (UTC)

GRUB2 Installation

I moved GRUB2 installation after chroot. Otherwise it doesn't work. grub-bios is in /mnt, so we need to tell grub-install about it. But arch iso has grub 0.97, and installation - 2.00, so iso's grub doesn't understand installation's files. --Shuk (talk) 11:42, 23 July 2012 (UTC)

GRUB install failure

This doesn't work for me.

It looks so similar to the Beginners' Guide as to be almost redundant, but the first subtle difference I came across meant (for me) that this procedure failed where the Beginners' Guide succeeded.

Under "GRUB" you have:

"Install GRUB2 to the harddrive containing your boot partition before you chroot."

  # grub-install /dev/sda

doing so returns:

"Path /boot/grub is not readable by GRUB on boot. Installation is impossible. Aborting."

In the Beginners' Guide, this step takes place after chrooting, which (for me) works ok, (although the wording - "Install GRUB2 to the harddrive containing your boot partition before you chroot" - is the same, so I guess both wiki entries are at fault). --bananabrain

Link Elinks to wiki

Just read that elinks is included on install iso, maybe add an alias/script to allow loading of wiki guide installation guide? --Mr Green

Check MD5 with Windows

Maybe we should add a link to http://www.etree.org/md5com.html - so people know how to check the MD5 with windows. I would add it myself but the page is locked for edit :-( . --PMay (talk)

This info should be add to Beginner's Guide. -- Fengchao (talk) 03:26, 25 July 2012 (UTC)
QuickSFV is better, IMO. Personally I wouldn't add it at all. Downloading through BitTorrent means that the hash tree is checked, and unless you have a drive with bad sectors (in which case you have bigger issues than this), then you don't really need to verify it. -- DSpider (talk) 07:44, 25 July 2012 (UTC)

The method to set locale

The documentation sais to set the locale by:

  • Set locale preferences in /etc/locale.conf.

The documentation at locale sais that the locale can also be set at /etc/rc.conf. This is confusing and should be clarified. --PMay (talk)

It can be set in both files. The locale.conf file is used by systemd and is more portable across distributions. It's relatively new, so the rc.conf method existed previously (rc.conf is specific to Arch Linux). I think the locale page makes it pretty clear that both can be used. thestinger (talk) 08:27, 26 July 2012 (UTC)

Mention the other config files

The old installation guide said something about editing the other config files:

  • /etc/rc.conf
  • /etc/fstab
  • /etc/mkinitcpio.conf
  • /etc/modprobe.d/modprobe.conf
  • /etc/resolv.conf
  • /etc/hosts
  • /etc/locale.gen
  • /etc/pacman.d/mirrorlist
  • /etc/pacman.conf
  • /etc/crypttab

This guide does not even mention /etc/rc.conf which is one of the central config files of archlinux. That should be added. --PMay (talk)

Well I saw this: Beginners'_Guide#Configure_system so /etc/rc.conf isnot the official way to configure the system anymore... --PMay (talk)
True, but some clarification somewhere about exactly which bits of rc.conf are still necessary and which have been superceded (and by what) would be useful. So far it seems like just the first six lines of the LOCALIZATION section and the HOSTNAME line from the networking section. I'm still slightly in the dark here, but getting there. --bananabrain
Regarding rc.conf, a lot of information has been added to its man page. I'm not sure how well aligned the man page and wiki page for it are, might need some updating. In any case you don't need to change anything in rc.conf for a basic install, so anything regarding that should go into the Beginners' Guide. --Emiralle (talk) 16:59, 24 July 2012 (UTC)
The rc.conf page will need quite a bit of updating once initscripts >= 2012.07.5-1 moves to [core].
-- Jstjohn (talk) 17:06, 24 July 2012 (UTC)

No mentioning of SWAP

In the main-article I saw a link to "paritioning" and "create new filesystems" but none of them mention how to set up a swap-partition. I would link it under "Format partitions": https://wiki.archlinux.org/index.php/Swap

As Dave already said multiple times, this guide is intended as a check list. Swap is hardly different from normal partitions, most likely not needed on recent hardware and you can set it up later if it turns out you really need one. I don't see the need for a link here. --Bluewind (talk) 12:56, 26 July 2012 (UTC)

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

Please add the interlanguage link to Installation Guide (한국어)

I translated Installation Guide into Korean, but I can't edit the English version to insert the interlanguage link to the Korean version Installation Guide (한국어). Would an administrator do it for me? Thank you in advance.--Kentarch (talk) 04:14, 27 July 2012 (UTC)

Done. -- Kynikos (talk) 08:43, 1 August 2012 (UTC)

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


Change PS1 during chroot

Be handy for some users to export PS1="[ chroot ]" maybe minor change to arch-chroot script Mr Green


As this guide mentions the loading of keymaps using loadkeys there should be at least a very small example about /etc/vconsole.conf

Either not talk about keymaps or tell how to make it correct. When this is used as a checklist, the setup of the keymap should not be missing.

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)

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)