Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/threatcode/threatos
https://github.com/threatcode/threatos
Last synced: 4 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/threatcode/threatos
- Owner: threatcode
- License: gpl-2.0
- Created: 2024-01-10T10:45:48.000Z (about 1 year ago)
- Default Branch: threatos-arm
- Last Pushed: 2024-01-28T09:50:58.000Z (about 1 year ago)
- Last Synced: 2024-04-16T05:17:12.793Z (10 months ago)
- Language: Shell
- Homepage: https://threatcode.github.io/ThreatOS/
- Size: 8.5 MB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## Threatos-ARM Build-Scripts
Threatos Linux ARM build-scripts.
These are the same build scripts that we use to generate the pre-generated official Threatos Linux ARM images, found here:
There are additional scripts included in this repository, supporting more devices, but these will need to be built in order for them to be used.
For more information, please see:
---
### Building
- These scripts are tested on Threatos Linux `arm64`, `x64`, and `x86` installations only _(We **recommend x64**)_
- Make sure you run the `./common.d/build_deps.sh` script before trying to build an image, as this installs all required dependencies. You may need to reboot after installing the build dependencies, if you do, the script will mention it at the end.
- You will need at **least 8GB of RAM or use SWAP file**
An example workflow to build a _[Raspberry Pi 4](https://threatcode.github.io/docs/arm/raspberry-pi-4/) Threatos Linux image_ would look like:
```
$ cd ~/
$ git clone https://github.com/threatcode/threatos
$ cd ~/threatos-arm/
$ sudo ./common.d/build_deps.sh
$ sudo ./raspberry-pi.sh
```
- Depending on your system hardware & network connectivity, will depend on how long it will take to build _(4 core CPU, 8GB RAM, SSD inside a VM takes using a [local repo](https://threatcode.github.io/docs/community/setting-up-a-threatos-linux-mirror/) about 100 minutes per script)_
- On x64 systems, after the script finishes running, you will have an image file located in `~/threatos-arm/images/` called `threatos-linux-2021.3-rpi-armhf.img.xz`
- On x86 systems, as they do not have enough RAM to compress the image, after the script finishes running, you will have an image file located in `~/threatos-arm/images/` called `threatos-linux-2021.3-rpi-armhf.img`
- _Should you want to try and shrink the file to make it easier to distribute, you will need to use **your own preferred compression**_.
---
### Help
On any build script, add `--help`. Example:
```
$ ./raspberry-pi.sh --help
Usage commands:
# Architectures (arm64, armel, armhf)
./raspberry-pi.sh --arch arm64 or ./raspberry-pi.sh -a armhf
# Desktop manager (xfce, gnome, kde, i3, lxde, mate, e17 or none)
./raspberry-pi.sh --desktop kde or ./raspberry-pi.sh --desktop=kde
# Minimal image - no desktop manager
./raspberry-pi.sh --minimal or ./raspberry-pi.sh -m
# Slim image - no desktop manager & cli tools
./raspberry-pi.sh --slim or ./raspberry-pi.sh -s
# Enable debug & log file (./logs/.log)
./raspberry-pi.sh --debug or ./raspberry-pi.sh -d
# Perform extra checks on the images build
./raspberry-pi.sh --extra or ./raspberry-pi.sh -x
# Help screen (this)
./raspberry-pi.sh --help or ./raspberry-pi.sh -h
```
---
### Custom Values
Changing [builder.txt](builder.txt.example) will allow for custom values, such as using a local LAN mirror:
```
$ echo 'mirror="http://192.168.1.100/threatos"' > ./builder.txt
```
---
Thu Jan 27 15:47:28 UTC 2022