:::note[TODO]
This article is a work in progress.
:::
Apostrophy OS is built on a system with the following specifications:
| Hardware | Make/Model/Qty |
|---|---|
| CPU | AMD Threadripper Pro |
| Memory | 512 GB DDR4 3200Mhz RAM [^1] |
| Disk | 4x 4TB Kingston NVMe |
| 10x Western Digital 4TB Red Caviar | |
| OS | Fedora (current or current minus one) |
| Airco | ecofort CoolAir 9+ (because AMD [^2]) |
| UPS | APC Pro 1600 S [^3] |
The signing system is a different system, about which you could dream, or speculate, or care less.
While you may of course originally develop in a hierarchy located at /home/your-username/devel/src/aphy/aphyos/build-topic1/, it should be noted this path can become too long for certain build commands (and effectively run out of MAX_ARGS_LEN).
If you encounter errors such as the following
$ make vts (...) posix_spawn: Argument list too long 09:42:16 ninja failed with: exit status 1 #### failed to build some targets (03:00 (mm:ss)) ####
then perhaps temporarily (or permanently) bind-mount to an effectively much shorter path length as examplified below, keeping in mind to perform at least one clean build.
$ sudo mkdir /srv/aphy $ sudo mount -o bind \ /home/your-username/devel/src/aphy/aphyos/build-topic1/ \ /srv/aphy $ cd /srv/aphy
[^1]: It shouldn't really take that much, but the release engineer's favorite editor is emacs, OK?
[^2]: It's not just a meme.
[^3]: Not even XFS on NVMe is fast enough to risk corrupting up to 16TB worth of small files.