A fork of SystemRescue (formerly SystemRescueCd) with ZFS built-in and serial console access enabled for all boot options. Download bootable ISOs from the releases page.
Find a file
2020-09-28 08:06:00 +01:00
airootfs Updated comments regarding the use of pacman (#150) 2020-09-27 20:19:51 +01:00
efiboot/grub Revert original name when related to boot config 2020-09-13 20:51:08 +01:00
isolinux Revert original name when related to boot config 2020-09-13 20:51:08 +01:00
patches srm patch: override airootfs files 2020-08-09 21:29:11 -03:00
syslinux Revert original name when related to boot config 2020-09-13 20:51:08 +01:00
.gitignore SystemRescueCd-6.0.0 2019-02-02 11:22:52 +00:00
build.sh Updated the ISO label 2020-09-28 08:06:00 +01:00
ChangeLog Rename project : SystemRescueCd ==> SystemRescue 2020-09-12 11:47:11 +01:00
LICENSE Updated LICENCE to follow archiso 2020-07-30 19:54:19 +01:00
mkinitcpio.conf Added encrypt hook to be able to boot from an encrypted disk (#108) 2020-05-25 14:00:56 +01:00
packages Add and enable qemu-guest-agent (#148) 2020-09-10 08:18:12 +01:00
pacman.conf Update website address 2020-09-13 13:42:13 +01:00
README.md Update website address 2020-09-13 13:42:13 +01:00
VERSION SystemRescueCd-6.1.8 2020-09-12 08:40:19 +01:00

SystemRescue

Project website

Homepage: https://www.system-rescue.org/

Project sources

This git repository contains SystemRescue sources files. This is based on https://gitlab.archlinux.org/archlinux/archiso/

Building SystemRescue

SystemRescue can be built for x86_64 or i686 architectures. It must be built on archlinux if you want to build a 64bit edition, or archlinux32 if you want to create a 32bit edition. The following packages must be installed on the build system: archiso, grub, mtools. You need to use a modified version of archiso for the build to work and for additional fixes and features to be present. You can find the required archiso version and patches in the "patches" folder in this git repository.

The package list contains packages which are not part of the official binary package repositories. These packages need to be built from sources from the AUR website. These sources are made of at least a PKGBUILD file and quite often other related files, such as patches. These can be built using the makepkg command which generates binary packages. These binary packages must be copied to a custom package repository which can be hosted locally using httpd or nginx. The repo-add command must be used to generate the repository package index. The pacman.conf file must be updated with the address of this repository so custom packages can be accessed.

The build process can be started by running the build.sh script. It will create a large "work" sub-directory and the ISO file will be written in the "out" sub-directory.