4421a2bc75
This prevents huge dependency downloads by pacman when the SystemRescue version gets older by using a snapshot repo from the day the SystemRescue version is released. The classic rolling repos from Arch are also available as option. Activate with the "--config /etc/pacman-rolling.conf" option to pacman. To allow switching on a per-command basis, two different sets of remote package databases are required. But the local package database must be the same for both variants. This is achived by using two different DBPaths in the pacman config files and bind-mounting the local part together. pacman does not accept symlinks for this, so it must be a bind mount. |
||
|---|---|---|
| airootfs | ||
| efiboot/grub | ||
| isolinux | ||
| patches | ||
| srm | ||
| syslinux | ||
| .gitignore | ||
| build.sh | ||
| ChangeLog | ||
| LICENSE | ||
| mirrorlist-snapshot-i686 | ||
| mirrorlist-snapshot-x86_64 | ||
| mkinitcpio.conf | ||
| packages | ||
| pacman.conf | ||
| README.md | ||
| VERSION | ||
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, edk2-shell. 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.
Including your SystemRescueModules
If you want to include your own SystemRescueModules, place their srm files in the srm directory of the repository before running the build script.