Void Linux installer implemented in GNU Prolog.

void-pi is a Void Linux installer similar to void-installer.

It extends void-installer in several ways:

• provides predefined templates for LVM, and LUKS.
• provides predefined partitioning templates for block devices and BTRFS and ZFS.
• supports rEFInd, Limine, Syslinux, Gummiboot, and ZFSBootMenu boot managers
• supports EFISTUB boot loader
• supports multi-device configurations.
• supports either BIOS or UEFI, or both boot modes.
• installs and configures additional boot manager and file system related software.

void-pi works on Void with Intel or AMD x86 CPU. It wasn't tested with ARM CPUs.

• Boot from an installation ISO.
• Run ip a to get an IP address.
• From another computer run:
  • ssh anon@ip_address
  • sudo bash
  • Run void-pi.

sudo xbps-install -Suy xbps wget
wget https://github.com/sdbtools/void-pi/releases/latest/download/void-pi.x86_64.tgz
tar -xzf void-pi.x86_64.tgz
./void-pi

sudo xbps-install gprolog git
git clone https://github.com/sdbtools/void-pi.git
cd void-pi
./void-pi.pl
# or
gprolog --consult-file void-pi.pl

sudo xbps-install gprolog gcc git
git clone https://github.com/sdbtools/void-pi.git
cd void-pi
gplc --min-size void-pi.pl
./void-pi

• sudo btrbk run

• grub-mkconfig -o /boot/grub/grub.cfg

This option is to build a custom Void Linux image from the official void-mklive repository.

$ git clone --depth=1 https://github.com/void-linux/void-mklive.git
$ cd void-mklive
$ make
$ sudo ./build-x86-images.sh -- -p zfs

Download a pre-built hrmpf image.

This option is to build a custom Void Linux image from the official void-mklive repository.

$ git clone --depth=1 https://github.com/void-linux/void-mklive.git
$ cd void-mklive
$ make
$ sudo ./build-x86-images.sh -- -v linux6.7

• completely emulates void-installer.
• install from Void ISO or network.
• predefined templates for LVM, LUKS, and combinations of them.
• predefined partitioning templates.
• selected devices will be automatically cleaned up.
• TUI for setting up of file system features and options.
• TUI for setting up of mount options.
• TUI dynamically changes depending on selected template.
• uses /mnt for chroot by default.
• allows to use an alternative rootdir via --rootdir command line argument.
• all settings can be saved in a file and loaded on startup. File name is controlled via --config command line argument.
• passwords are never saved in files even temporarily.
• max password length is limited to 1024 charaters.
• Boot modes
  • UEFI
  • BIOS
  • both
• Boot managers
  • Uses GRUB, rEFInd, Limine, Syslnux, or Gummiboot as a boot manager.
  • Uses EFISTUB as a boot loader.
  • rEFInd is configured to use kernel auto detection.
  • Only GRUB can have /boot on LVM or LUKS.
  • ZFSBootMenu is enabled only with the "GPT. Basic" template at this time.
  • If a boot manager doesn't support a file system (or LVM, or LUKS), then installer will create an ext4 /boot partition.

• ZFS
  • Requires a ZFS install media.
  • Supported by GRUB and ZFSBootMenu bootmanagers.
  • In case of GRUB only "GPT. Basic" template is supported at this time.
  • Encryption can be enabled via "FS Settings".
  • In case of GRUB encryption shouldn't be used because GRUB doesn't support it.
• Bcachefs
  • Requires a Bcachefs install media.
• Syslinux
  • In case of UEFI the kernel and initramfs files are located in the EFI system partition (aka ESP), as Syslinux does not (currently) have the ability to access files outside its own partition.
  • IA32 (32-bit) is currently unsupported.
• EFISTUB
  • The kernel and initramfs files are located in the EFI system partition (aka ESP).
  • btrfs is not supported.
• Gummiboot
  • The kernel and initramfs files are located in the EFI system partition (aka ESP).
  • btrfs is not supported.
• ZFSBootMenu
  • Only direct EFI booting is supported at this time.
  • Enabled only with "Manual" and "GPT. Basic" templates at this time.
• LUKS
  • LUKS can be used with GRUB, rEFInd, Limine, and Syslinux.
  • Only GRUB can have /boot on LUKS.
  • In case of GRUB whole system is located on LUKS, including encrypted /boot. LUKS1 is used because GRUB2 doesn't support LUKS2.
  • In case of rEFInd and Limine installer will create an unencrypted ext4 /boot partition. LUKS2 is used.
• LVM
  • Only GRUB can have /boot on LVM.
• Multi-device support
  • Multi-device configurations are available with BTRFS and LVM.
• Additional software
  • snooze - run a command at a particular time.
  • btrbk - Tool for creating snapshots and remote backups of btrfs subvolumes.
  • grub-btrfs - improves the grub bootloader by adding a btrfs snapshots sub-menu, allowing the user to boot into snapshots.

• Manual configuration of everything
• GPT. Basic
• GPT. LVM
• GPT. LVM. LUKS
• GPT. LUKS. One device
• GPT. LUKS. LVM. One device

void-pi creates the following Btrfs subvolumes with a flat layout:

• root

• root_home

• max

• root

• root_home

• max

• root
  • / (size: whole device)
• root_home
  • / (size: 20GB)
  • /home (size: remainder)

All default settings can be changed via Common Attrs sub-menu.

• host-only: no
• installation source: local
• host name: voidpp
• user name: void
• keymap: us
• locale: en_US.UTF-8
• timezone: America/New_York
• LUKS mapping name: crypt
• MBR size: 1M
• ESP size: 550M
• Boot partition size: 1G
• btrbk: /mnt/btr_pool
  • snapshots are created for @, @opt, @var, @srv, and @home subvolumes.
  • btrbk is scheduled to run every day

• Limine and Syslinux
  • /dev/sdX1 is the root filesystem (size: whole device)
• Grub
  • /dev/sdX1 is the BIOS boot sector (size: 1M)
  • /dev/sdX2 is the root filesystem (size: remainder)

• /dev/sdX1 is the EFI system partition (size: 550M)
• /dev/sdX2 is the root filesystem (size: remainder)

• extra_attr,inode_checksum,sb_checksum,compression,encrypt

This software is released under the GNU GPLv2 license.

• Void Linux
• Voidvault