BRO PLEASE SWITCH BASE TO ARCH LINUX ITS UNSTABLE

[Ardaninho]

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 ISO PGP signature (under Checksums in the page Download) to the ISO directory, and verifying it with:

$ gpg --keyserver-options auto-key-retrieve --verify archlinux-version-x86_64.iso.sig

Alternatively, from an existing Arch Linux installation run:

$ pacman-key -v archlinux-version-x86_64.iso.sig Note: The signature itself could be manipulated if it is downloaded from a mirror site, instead of from archlinux.org as above. In this case, ensure that the public key, which is used to decode the signature, is signed by another, trustworthy key. The gpg command will output the fingerprint of the public key. Another method to verify the authenticity of the signature is to ensure that the public key's fingerprint is identical to the key fingerprint of the Arch Linux developer who signed the ISO-file. See Wikipedia:Public-key cryptography for more information on the public-key process to authenticate keys. 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 Note: Arch Linux installation images do not support Secure Boot. You will need to disable Secure Boot to boot the installation medium. If desired, Secure Boot can be set up after completing the installation. 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. When the installation medium's boot loader menu appears, select Arch Linux install medium and press Enter to enter the installation environment. Tip: The installation image uses GRUB for UEFI and syslinux for BIOS booting. See README.bootparams for a list of boot parameters. You will be logged in on the first virtual console as the root user, and presented with a Zsh shell prompt. 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 pkglist.x86_64.txt 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:

ls /usr/share/kbd/keymaps/*/.map.gz

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

loadkeys de-latin1

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:

ls /sys/firmware/efi/efivars

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

ip link

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:

ping archlinux.org

Note: If the disk does not show up, make sure the disk controller is not in RAID mode. If the disk from which you want to boot already has an EFI system partition, do not create another one, but use the existing partition instead. Swap space can be set on a swap file for file systems supporting it. UEFI with GPT /mnt/boot /dev/efi_system_partition EFI system partition At least 300MiB [SWAP] /dev/swap_partition Linux swap More than 512 MiB /mnt /dev/root_partition Linux x86-64 root (/) Remainder of the device Other mount points, such as /mnt/efi, are possible, provided that 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. BIOS with MBR [SWAP] /dev/swap_partition Linux swap More than 512 MiB /mnt /dev/root_partition Linux Remainder of the device See also Partitioning#Example layouts.

Format the partitions Once the partitions have been created, each newly created partition must be formatted with an appropriate file system. See File systems#Create a file system for details.

For example, to create an Ext4 file system on /dev/root_partition, run:

mkfs.ext4 /dev/root_partition

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

mkswap /dev/swap_partition

Note: For stacked block devices replace /dev/*_partition with the appropriate block device path. If you created an EFI system partition, format it to FAT32 using mkfs.fat(8).

Warning: Only format the EFI system partition if you created it during the partitioning step. If there already was an EFI system partition on disk beforehand, reformatting it can destroy the boot loaders of other installed operating systems.

mkfs.fat -F 32 /dev/efi_system_partition

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

mount /dev/root_partition /mnt

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

Tip: Run mount(8) with the --mkdir option to create the specified mount point. Alternatively, create it using mkdir(1) beforehand. For UEFI systems, mount the EFI system partition:

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

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

swapon /dev/swap_partition

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.

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:

pacstrap -K /mnt base linux linux-firmware

Tip: You can substitute linux for a kernel package of your choice, or you could omit it entirely when installing in a container. You could omit the installation of the firmware package when installing in a virtual machine or container. 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 (e.g. a network manager or DHCP client), 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 pkglist.x86_64.txt. Configure the system Fstab Generate an fstab file (use -U or -L to define by UUID or labels, respectively):

genfstab -U /mnt >> /mnt/etc/fstab

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

Chroot Change root into the new system:

arch-chroot /mnt

Time zone Set the time zone:

ln -sf /usr/share/zoneinfo/Region/City /etc/localtime

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

hwclock --systohc

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:

locale-gen

Create the locale.conf(5) file, and set the LANG variable accordingly:

/etc/locale.conf LANG=en_US.UTF-8 If you set the console keyboard layout, make the changes persistent in vconsole.conf(5):

/etc/vconsole.conf KEYMAP=de-latin1 Network configuration Create the hostname file:

/etc/hostname myhostname 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:

mkinitcpio -P

Root password Set the root password:

passwd

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.

[ghost]

another le dishery lol

[Ardaninho]

NOW DONT LOCK CLOSE

[dominichayesferen]

Two of your issues have already been closed for spam. If you do it again, I'll be forced to ban you from this repository entirely, meaning you'll never be able to report actual bugs whatsoever. If there was a team of multiple members, here, you would literally be wasting the time of those doing bug triaging with issues like these, just like you are currently wasting my time right now that I could use working on Feren OS.

This is a bug reporting center, not your playground to do whatever you want. Please remember to adhere to the https://docs.github.com/articles/github-community-guidelines, as breaching it can make you lose your GitHub account entirely.