3b2eaf953b
Create SystemRescueModules (SRM) from pacman packages installed into the COW space This script is meant to help creating SystemRescueModules (SRM) for SystemRescue. More info about SRMs and this script can be found at: https://www.system-rescue.org/Modules/ To use first install all packages you want to have in your SRM with pacman. Default COW (Copy-On-Write) space is a ramdisk, so you usually don't have to do anything special except provide enough RAM. You can also enable any systemd services that are in these packages. Then call: cowpacman2srm [-c compalg] [-l complevel] targetfile.srm Copy the .srm file to archisobasedir (default: "sysresccd") on your boot disk and add the "loadsrm" boot parameter to SystemRescue. There is no mechanism to check if a SRM is compatible with the version of SystemRescue you are trying to run it with. So it is higly recommended to only use this script on the exact version of SystemRescue you plan to use the SRM with. |
||
|---|---|---|
| airootfs | ||
| efiboot/grub | ||
| isolinux | ||
| patches | ||
| syslinux | ||
| .gitignore | ||
| build.sh | ||
| ChangeLog | ||
| LICENSE | ||
| 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.