diff options
author | Lars Wirzenius <liw@liw.fi> | 2023-08-01 14:45:46 +0000 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2023-08-01 14:45:46 +0000 |
commit | 00283077ae7e254326b151085043b45176fc63f6 (patch) | |
tree | ea3ea0aad7a53dfb9c689454ba070d454e1fff1d | |
parent | 115806eaa7858e285c211958641762e57e9dc497 (diff) | |
parent | 134e01cc0da7a75c786b5f84ff90b4a2aec23f89 (diff) | |
download | ambient-ci-00283077ae7e254326b151085043b45176fc63f6.tar.gz |
docs: clarify architecture description of build VM
See merge request larswirzenius/ambient-ci!32
-rw-r--r-- | ambient.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -259,12 +259,16 @@ At a very abstract level, the Ambient architecture is as follows: - `/dev/vdc`: the read/write artifact device: for the project to write a tar archive of any build artifacts it wants to export - this would be write-only if that was possible + - when the build starts, this contains only zeroes + - after the build a tar archive is extracted from this - `/dev/vdd`: the read-only dependencies device: a tar archive of additional dependencies in a form that the project can use - `/dev/vde`: the read/write cache device: a tar archive of any files the project wants to persist across runs; for example, for a Rust project, this would contains the cargo target directory contents + - when a build starts, this can be empty; the build must deal with + an empty cache * The VM additionally has a serial port where it will write the build log. On Linux this is `/dev/ttyS0`. * The VM automatically, on boot, creates |