2020-09-12 12:27:37 +02:00
|
|
|
# SystemRescue
|
2019-02-02 12:22:52 +01:00
|
|
|
|
2020-02-02 10:04:30 +01:00
|
|
|
## Project website
|
2020-09-13 14:42:13 +02:00
|
|
|
Homepage: https://www.system-rescue.org/
|
2019-02-02 12:22:52 +01:00
|
|
|
|
2020-02-02 10:04:30 +01:00
|
|
|
## Project sources
|
2020-09-12 12:27:37 +02:00
|
|
|
This git repository contains SystemRescue sources files. This is based on
|
2020-08-07 18:48:20 +02:00
|
|
|
https://gitlab.archlinux.org/archlinux/archiso/
|
2020-02-02 10:04:30 +01:00
|
|
|
|
2020-09-12 12:27:37 +02:00
|
|
|
## Building SystemRescue
|
|
|
|
|
SystemRescue can be built for x86_64 or i686 architectures. It must be built
|
2020-03-07 17:18:46 +01:00
|
|
|
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
|
2020-10-12 21:30:31 +02:00
|
|
|
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.
|
2020-02-02 10:04:30 +01:00
|
|
|
|
|
|
|
|
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.
|
