web/install1.md

Back to the top joborun wiki page

..nack to installation main menusection 1.

1 First create a new partition for the system to be created. If you don't know how, see the great wiki.archlinux.org wiki on the subject. We will only provide here information that is different than Arch Linux or Obarun.

% cd /tmp
% wget https://git.disroot.org/joborun-pkg/jobcore/raw/branch/main/pacman/pac-inst.conf

This will get you a copy of joborun's pacman.conf file without the need for a separate mirrorlist, as it is now the default joborun setup.

For simplicity we will refer to this prepared and mounted partition as the "target" /mnt and the arch system from which you will make the installation will be the "host" /

For EFI systems also follow the wiki entry UEFI or the arch wiki EFI system partition.

Assumptions for this installation:

• User has partitioned, formatted, and mounted partitions on /mnt
• Network is functional
• Arguments passed to the script are valid pacman targets
• A valid mirror appears in /etc/pacman.d/mirrorlist
• You are in a root shell
• arch-install-scripts is installed in your system (includes arch-chroot & genfstab which will be used here)

One of the key differences with Arch is that joborun and Obarun have a few more repositories that are placed higher up in hierarchy within /etc/pacman.conf to give priority to joborun's packages over Obarun, and Obarun's packages over arch. (Obarun's packages other than s6/66 are generally rebuilds without systemd/libs running dependencies. Joborun's packages over Arch are rebuilds without systemd/libs makedependencies).

Create pacman lib directory in /mnt

# mkdir -p /mnt/var/lib/pacman

This is necessary for installing pacman to the target in order to use the current and correct joborun pacman.conf.

install joborun's pacman to target

# pacman -Sy pacman --config /tmp/pac-inst.conf -r /mnt
# pacman -Sy base opensysusers** linux(***) -r /mnt

** Sysusers should be used in lack of systemd to set systemd IDs for special users like systemd does. With the use of s6 and 66 obsysusers is a dependency and replaces opensysusers. Basically it is the same script and runs through a pacman hook reading a sysusers.d directory for users settings by any software that require to execute something as a special system user (neither a regular user or root).

*** You have a choice of joborun's special linux-lts (5.10) or linux (5.15) and if you need linux/linux-lts headers add them to the list. Same for linux-firmware, especially if you have an AMD machine with Radeon gfx card, you will not get anything on screen without it. There are also less frequently maintained kernel's 4.9 5.4 6.0 6.1 6.4 6.5 ...

We highly recommend linux-lts (5.10) as a very well developed kernel expiring in 2026, while 5.15 is expected to last only till 2024. So 5.10 is a longer LTS, while 5.15 is a relative short term LTS. Current late lts is 6.1 carried by Arch while 6.2 is current stable. So the choices are wide.

If you want additional packages you can either do this later through chroot or add them at the end of the above command (ie networking package of choice, text editor, arch-install-scripts, bootloader-grub/syslinux, etc. ). We are trying to make sure you have a fully functional system to boot and login to console, then you can install whatever you like.

Select the closest mirrors to your location and remove the comment sign '#' from in front of them. Pacman hits the first uncommented server on the list and only if it fails goes to the next. You do this by editing: /etc/pacman.d/mirrorlist and /etc/pacman.d/mirrorlist-jobo

This is a screened list from Arch to only include https:// mirrors, so some countries' mirrors that only offer an http:// service have been ommitted. You can always replace our https only mirrorlist with mirrorlist-arch which includes the http: only sites (an exact copy of the current arch mirrorlist).

The following is about the same as running joborun-setup from (jobo-setup) pkg. Install jobo-setup and execute the joborun-setup script to take care of the rest of the configuration. Alternatively take care of the following:

# $EDITOR /mnt/etc/pacman.d/mirrorlist

Initialize pacman, re-populate its gpg-keys and update the database

# arch-chroot /mnt pacman-key --init
# arch-chroot /mnt pacman-key --populate joborun archlinux obarun
# arch-chroot /mnt pacman -Syu

Select the lingual group of your installation by removing the '#' (uncommenting - example: "en_US.UTF-8 UTF-8" for US English ) and pass the choice into the system:

# $EDITOR /mnt/etc/locale.gen

# arch-chroot /mnt locale-gen

If you are working in chroot don't expect the change in locale to be automatic, you must either restart a shell, or exit and re-enter, or in a booted system relogin. By reboot it will for sure change the language.

Create an fstab entry of your new installation:

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

Create a root password

# arch-chroot /mnt passwd

edit your hosts as per your network needs

# $EDITOR /mnt/etc/hosts

edit your hostname, although it should also be set by configuring your boot module in 66 or editing /etc/rc.conf for runit.

# $EDITOR /mnt/etc/hostname

7 Misc. optional configurations

Install and set your boot loader as per Obarun and/or arch wikis if necessary:

grub syslinux UEFI

We have also built the limine boot loader software which is simple and one configuration works on both MBR/Bios booting and GPT/UEFI boot. Unfortunately it will not work with btrfs or xfs yet, so use grub if you choose those filesystems.

#Note

Your installation is complete

You may either reboot at this point or use arch-chroot to get into the installation and do more configurations or pkg installations as you need.

Welcome to joborun

Note: In general, the hierarchy as seen in pacman.conf works in reverse for wiki. What you can not find here you may find in Obarun, as it applies here as well. What you can't find in Obarun wiki you can find in wiki.archlinux.org, and it applies for Obarun, and applies here as well. With the exception of anything that relates to systemd/logind. On the other side of the coin though there may be a tendency to overbrowse Artix wiki, and with the very specific runit similarity there is nothing that should be relevant, compatible, and non-destructive.