System install packages linux

Installation guide

This document is a guide for installing Arch Linux using the live system booted from an installation medium made from an official installation image. The installation medium provides accessibility features which are described on the page Install Arch Linux with accessibility options. For alternative means of installation, see Category:Installation process.

Before installing, it would be advised to view the FAQ. For conventions used in this document, see Help:Reading. In particular, code examples may contain placeholders (formatted in italics ) that must be replaced manually.

For more detailed instructions, see the respective ArchWiki articles or the various programs’ man pages, both linked from this guide. For interactive help, the IRC channel and the forums are also available.

Arch Linux should run on any x86_64-compatible machine with a minimum of 512 MiB RAM, though more memory is needed to boot the live system for installation.[1] A basic installation should take less than 2 GiB of disk space. As the installation process needs to retrieve packages from a remote repository, this guide assumes a working internet connection is available.

Contents

Pre-installation

Acquire an installation image

Visit the Download page and, depending on how you want to boot, acquire the ISO file or a netboot image, and the respective GnuPG signature.

Verify signature

It is recommended to verify the image signature before use, especially when downloading from an HTTP mirror, where downloads are generally prone to be intercepted to serve malicious images.

On a system with GnuPG installed, do this by downloading the PGP signature (under Checksums in the Download page) to the ISO directory, and verifying it with:

Alternatively, from an existing Arch Linux installation run:

Prepare an installation medium

The installation image can be supplied to the target machine via a USB flash drive, an optical disc or a network with PXE: follow the appropriate article to prepare yourself an installation medium from the chosen image.

Boot the live environment

1. Point the current boot device to the one which has the Arch Linux installation medium. Typically it is achieved by pressing a key during the POST phase, as indicated on the splash screen. Refer to your motherboard’s manual for details.
2. When the installation medium’s boot loader menu appears, select Arch Linux install medium and press Enter to enter the installation environment.

To switch to a different console—for example, to view this guide with Lynx alongside the installation—use the Alt+arrow shortcut. To edit configuration files, mcedit(1) , nano and vim are available. See packages.x86_64 for a list of the packages included in the installation medium.

Set the console keyboard layout

The default console keymap is US. Available layouts can be listed with:

To modify the layout, append a corresponding file name to loadkeys(1) , omitting path and file extension. For example, to set a German keyboard layout:

Console fonts are located in /usr/share/kbd/consolefonts/ and can likewise be set with setfont(8) .

Verify the boot mode

To verify the boot mode, list the efivars directory:

If the command shows the directory without error, then the system is booted in UEFI mode. If the directory does not exist, the system may be booted in BIOS (or CSM) mode. If the system did not boot in the mode you desired, refer to your motherboard’s manual.

Connect to the internet

To set up a network connection in the live environment, go through the following steps:

• Ensure your network interface is listed and enabled, for example with ip-link(8) :
• For wireless and WWAN, make sure the card is not blocked with rfkill.
• Connect to the network:
  • Ethernet—plug in the cable.
  • Wi-Fi—authenticate to the wireless network using iwctl.
  • Mobile broadband modem—connect to the mobile network with the mmcli utility.
• Configure your network connection:
  • DHCP: dynamic IP address and DNS server assignment (provided by systemd-networkd and systemd-resolved) should work out of the box for Ethernet, WLAN and WWAN network interfaces.
  • Static IP address: follow Network configuration#Static IP address.
• The connection may be verified with ping:

Update the system clock

Use timedatectl(1) to ensure the system clock is accurate:

To check the service status, use timedatectl status .

Partition the disks

When recognized by the live system, disks are assigned to a block device such as /dev/sda , /dev/nvme0n1 or /dev/mmcblk0 . To identify these devices, use lsblk or fdisk.

Results ending in rom , loop or airoot may be ignored.

The following partitions are required for a chosen device:

If you want to create any stacked block devices for LVM, system encryption or RAID, do it now.

Use fdisk or parted to modify partition tables. For example:

Example layouts

BIOS with MBR

Mount point	Partition	Partition type	Suggested size
[SWAP]	/dev/swap_partition	Linux swap	More than 512 MiB
/mnt	/dev/root_partition	Linux	Remainder of the device

UEFI with GPT

Mount point	Partition	Partition type	Suggested size
/mnt/boot or /mnt/efi 1	/dev/efi_system_partition	EFI system partition	At least 260 MiB
[SWAP]	/dev/swap_partition	Linux swap	More than 512 MiB
/mnt	/dev/root_partition	Linux x86-64 root (/)	Remainder of the device

1. /mnt/efi should only be considered if the used boot loader is capable of loading the kernel and initramfs images from the root volume. See the warning in Arch boot process#Boot loader.

Format the partitions

Once the partitions have been created, each newly created partition must be formatted with an appropriate file system. For example, to create an Ext4 file system on /dev/root_partition , run:

If you created a partition for swap, initialize it with mkswap(8) :

Mount the file systems

Mount the root volume to /mnt . For example, if the root volume is /dev/root_partition :

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

If you created a swap volume, enable it with swapon(8) :

genfstab(8) will later detect mounted file systems and swap space.

Installation

Select the mirrors

Packages to be installed must be downloaded from mirror servers, which are defined in /etc/pacman.d/mirrorlist . On the live system, after connecting to the internet, reflector updates the mirror list by choosing 20 most recently synchronized HTTPS mirrors and sorting them by download rate.[2]

The higher a mirror is placed in the list, the more priority it is given when downloading a package. You may want to inspect the file to see if it is satisfactory. If it is not, edit the file accordingly, and move the geographically closest mirrors to the top of the list, although other criteria should be taken into account.

This file will later be copied to the new system by pacstrap, so it is worth getting right.

Install essential packages

Use the pacstrap(8) script to install the base package, Linux kernel and firmware for common hardware:

The base package does not include all tools from the live installation, so installing other packages may be necessary for a fully functional base system. In particular, consider installing:

• userspace utilities for the management of file systems that will be used on the system,
• utilities for accessing RAID or LVM partitions,
• specific firmware for other devices not included in linux-firmware (e.g. sof-firmware for sound cards),
• software necessary for networking,
• a text editor,
• packages for accessing documentation in man and info pages: man-db , man-pages and texinfo .

To install other packages or package groups, append the names to the pacstrap command above (space separated) or use pacman while chrooted into the new system. For comparison, packages available in the live system can be found in packages.x86_64.

Configure the system

Fstab

Generate an fstab file (use -U or -L to define by UUID or labels, respectively):

Check the resulting /mnt/etc/fstab file, and edit it in case of errors.

Chroot

Change root into the new system:

Time zone

Run hwclock(8) to generate /etc/adjtime :

This command assumes the hardware clock is set to UTC. See System time#Time standard for details.

Localization

Edit /etc/locale.gen and uncomment en_US.UTF-8 UTF-8 and other needed locales. Generate the locales by running:

Network configuration

Add matching entries to hosts(5) :

If the system has a permanent IP address or a fully qualified domain name, see the example in Network configuration#Local hostname resolution.

Complete the network configuration for the newly installed environment, that may include installing suitable network management software.

Initramfs

Creating a new initramfs is usually not required, because mkinitcpio was run on installation of the kernel package with pacstrap.

For LVM, system encryption or RAID, modify mkinitcpio.conf(5) and recreate the initramfs image:

Root password

Boot loader

Choose and install a Linux-capable boot loader. If you have an Intel or AMD CPU, enable microcode updates in addition.

Reboot

Exit the chroot environment by typing exit or pressing Ctrl+d .

Optionally manually unmount all the partitions with umount -R /mnt : this allows noticing any «busy» partitions, and finding the cause with fuser(1) .

Finally, restart the machine by typing reboot : any partitions still mounted will be automatically unmounted by systemd. Remember to remove the installation medium and then login into the new system with the root account.

Post-installation

See General recommendations for system management directions and post-installation tutorials (like creating unprivileged user accounts, setting up a graphical user interface, sound or a touchpad).

For a list of applications that may be of interest, see List of applications.

Источник

System install packages linux

Modern systems based on Linux include a huge number of resources commonly used by many programs, such as shared libraries of standard functions, executable files, scripts and standard utilities necessary for the normal work of many programs. Removal or upgrade of one of the system components may cause other dependent components to stop functioning correctly or even make the entire system inoperable. In the context of system administration such problems are called loss of system integrity. The goal of an administrator is to ensure that the system contains compatible versions of all the necessary components (system integrity control).

To install, delete and update program packages and to maintain the integrity of the Linux system, package managers (such as RPM in RedHat distributions or dpkg in Debian GNU/Linux) began to be used primarily. For a package manager, software consists of sets of components known as software packages. Such components contain sets of executables and auxiliary files needed for the correct work of software. Package managers unify and automate the process of building binary packages and make program installation easier, allowing to directly check for availability of components with the required versions at installation time, and performing all the procedures necessary to register the program in all the user operating environments. As soon as installation is completed, the program becomes available to from the command prompt and appears in the menus of all the graphical environments.

Important

Thanks to package managers, Linux users usually do not need to call the installation procedures of individual applications directly, or to directly interact with directories in which executable files and other program components are installed (these normally are /usr/bin and /usr/share/ package_name). All this work is done by a package manager. This is why program installation, uninstallation and upgrade are usually referred to as package management in Linux.

Components used by different programs are often gathered in separate packages. Package A, needed for software included in Package B to function, is marked in a special way. In this case it is said that Package B depends on Package A, or that there exists a dependency between packages A and B.

Tracking dependencies among such packages is a serious task for any Linux distribution. Some packages may be mutually replaceable, there may be several packages containing a required resource.

The task of controlling integrity and consistency of software installed in the system is more difficult. Let us imagine that certain programs A and B require the presence of component C, version 1.0, in the system. Update of package A, which requires upgrading of component C to a new version (let’s say 2.0) that provides a new access interface, will thus necessarily lead to the update of program B.

However, package managers are not always capable of preventing all possible errors during program installation and uninstallation. Neither can they effectively restore system integrity. This defect is especially obvious when the system is updated from a centralized repository of packages, in which packages are continuously updated and sometimes split into smaller ones etc. This problem stimulated the creation of software package management and integrity maintenance systems.

To automate this process, the Advanced Packaging Tool ( APT ) is used. Such automation is achieved by creating one or several external repositories, in which program packages are stored. Packages installed in the system are checked against these repositories. A repository may contain an official version of a distribution, updated by developers as new versions of programs are released. However, it may also contain packages developed locally, for instance, builds of internal company projects.

Thus there are two databases at the disposal of APT : one describes packages installed in the system, the second one describes the external repository. APT keeps track of integrity of the installed system, and, if any inconsistencies in package dependencies are discovered, it uses data from the external repository to resolve conflicts and to find a correct way to fix the problem.

APT was initially developed to manage installation and removal of programs in the Debian GNU/Linux distribution. During development, the goal of replacing dselect , a package selection utility used in Debian, with a new one was set. The new system had to have wider functionality and a simple user interface. It also had to allow users to perform installation, updates and routine management of programs installed on a computer without the need to study subtleties of a software package manager used in the distribution.

Such attractive features had for a long time been available only to Debian users, because only one package manager had been supported by APT , namely the dpkg package manager, used in Debian, incompatible with RPM , used in ALT Linux. This incompatibility mostly lies in different data formats (although converter applications exist), but there are also other differences, which are outside the scope of this description.

However, APT was initially conceived as independent of the particular method of handling packages installed in the system, and this peculiarity allowed developers from the Brazilian company Conectiva to implement the support of RPM package manager in it. Thus users of distributions based on RPM (ALT Linux being one of them) gained an opportunity to use this powerful tool.

APT is at the present time still in its development stage, and the current version that supports RPM is classified as unstable. This, however, does not mean that operations carried out with the help of APT will inevitably make the system unstable. On the contrary, strict control over the system integrity is possible with APT : broken dependencies between installed packages can be checked and the found errors can be corrected.

Источник