Skip to main content

ArchLinux Installation EFI

Installing ArchLinux with UEFI

The official ArchLinux installation page is very good, but obviously cannot cover all installation scenario.

I had to install with EFI and steps are not straight copy/paste of that page.

I will make the log story short but just pasting the commands and indicate what is needed and not in the guide.

ping archlinux.org
timedatectl set-ntp true
Use parted instead of fdisk
parted /dev/sda
Print existing partitions and clear them all:
(parted) print
(parted) rm 1
(parted) rm 2
(parted) rm ...
Create the EFI partition and fill the remaining
(parted) mklabel gpt
(parted) mkpart ESP fat32 1MiB 513MiB
(parted) set 1 boot on
(parted) mkpart primary btrfs 513MiB 100%
(parted) print
(parted) quit
Note that in "parted", "quit" also saves (in "fdisk", "quit" does not)

Format and mount created partitions
mkfs.fat -F32 /dev/sda1
mkfs.btrfs /dev/sda2
mount /dev/sda2 /mnt
mkdir -pv /mnt/boot/efi
mount /dev/sda1 /mnt/boot/efi
Here is just a small improve of the officiel guide: add some usefull packages to installation
pacstrap /mnt base base-devel dhclient openssh btrfs-progs grub efibootmgr
genfstab -U /mnt >> /mnt/etc/fstab
arch-chroot /mnt
The following is just copy/paste of https://wiki.archlinux.org/index.php/Installation_guide
ln -sfv /usr/share/zoneinfo/Indian/Antananarivo /etc/localtime
hwclock --systohc
echo 'en_US.UTF-8 UTF-8' > /etc/locale.gen
locale-gen
echo 'LANG=en_US.UTF-8' >  /etc/locale.conf
echo 'KEYMAP=fr' > /etc/vconsole.conf
echo 'hv-01' > /etc/hostname
echo '127.0.1.1 hv-01.rktmb.org hv-01' >> /etc/hosts
mkinitcpio -p linux
passwd
The EFI flavour "grub-install" is documented, but here it is:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub
grub-mkconfig -o /boot/grub/grub.cfg

You may now just exit the chroot and reboot on your new installation.

Comments

Popular posts from this blog

vmware net_device trans_start

VMWare Workstation 12 and Kernel 4.7 When recompiling vmware kernel modules on a kernel 4.7, I get this error:

/tmp/modconfig-xrrZGZ/vmnet-only/netif.c:468:7: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?     dev->trans_start = jiffies;
This seems to be an already encountered problem: http://rglinuxtech.com/?p=1746http://ferenc.homelinux.com/?p=356 I choosed to replace the line, instead of deleting it.

- dev->trans_start = jiffies; + netif_trans_update(dev); I also noted that I had to re-tar the modified sources instead of leaving them untared, because the compilation process only takes the archives. 
On precedent editions of these files, I just left the modified folders "vmnet-only/" and "vmmon-only/" expanded without the need to re-tar them.


Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…

dockerfile multiline to file

Outputing a multiline string from Dockerfile
I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian.
But I also have a local mirror and would like to use it for packages installation.

Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file.

Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write.
Here you are:

RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 " >>…