The zHIVErbox fork of the Armbian build tools tries to stick as close as possible to the upstream master branch and do customizations via our armbian-userpatches repository. However, a few modifications can't be done via the userpatches:
-
btrfs subvolumes for /, /home, /var and /var/lib zHIVErbox makes use of btrfs subvolumes, so we can easily move /var to the hard disk of the Odroid HC1/HC2 and disable log2ram, which slightly increases the available (free) memory on the zHIVErbox.
-
kernel self-protection and security hardenings zHIVErbox applies many kernel security settings described in:
- https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings
- https://tails.boum.org/contribute/design/kernel_hardening/ This can't be done via the armbian-userpatches, so we have to do this here.
-
cache directory for userpatches In addition to the
userpatches/overlaydirectory, zHIVErbox set's up auserpatches/cachedirectory, which is persisted across builds but doesn't contain any essential sources. It can be used by apt to speed up subsequent builds, as packages which are installed through userpatches don't have to be downloaded with every build when they have been downloaded with a previous build already. -
use btrfs with
lzocompression instead ofzlibVanilla Armbian doesn't allow the configuration of which compression should be used with btrfs. zHIVErbox adds this as a configuration option and useslzoby default, which gives slight performance improvements. -
minor changes 4.1. avoid username leaks in
armbian-check-first-login.sh4.2. use netcat with Tor socksproxy in armbian-config.sh4.3. use torsocks to pull zHIVErbox git updates incompile.sh
Debian based Linux for ARM based single-board computers
Supported build environment is Ubuntu Bionic 18.04 x64 (minimal iso image).
- guest inside a VirtualBox or other virtualization software,
- guest managed by Vagrant. This uses Virtualbox (as above) but does so in an easily repeatable way. Please check the Armbian with Vagrant README for a quick start HOWTO,
- inside a Docker, systemd-nspawn or other container environment (example),
- running natively on a dedicated PC or a server (not recommended),
- 20GB disk space or more and 2GB RAM or more available for the VM, container or native OS,
- superuser rights (configured
sudoor root access).
Execution
apt-get -y install git
git clone https://github.com/armbian/build
cd build
./compile.sh
Make sure that full path to the build script does not contain spaces.
You will be prompted with a selection menu for a build option, a board name, a kernel branch and an OS release. Please check the documentation for advanced options and additional customization.
Build process uses caching for the compilation and the debootstrap process, so consecutive runs with similar settings will be much faster.
Please read this notice first before opening an issue.
- Fork the project
- Make one or more well commented and clean commits to the repository.
- Perform a pull request in github's web interface.
If it is a new feature request, don't start the coding first. Remember to open an issue to discuss the new feature.
If you are struggling, check this detailed step by step guide on contributing.