@@ -17,23 +17,24 @@ There are currently four crates to know about:
1717
1818## The metallurgy metaphor
1919
20- Although end-users could probably ignore it, the internals of ` goldboot ` use vocabulary
21- taken from the field of metallurgy.
20+ Although end-users could probably ignore it, the internals of ` goldboot ` use
21+ vocabulary taken from the field of metallurgy.
2222
2323#### Foundry
2424
25- An image foundry is a configuration object that knows how to build goldboot images.
25+ An image foundry is a configuration object that knows how to build goldboot
26+ images.
2627
2728#### OS
2829
2930An image mold takes an image source and refines it according to built-in rules.
3031For example, the ` ArchLinux ` mold knows how to take Arch Linux install media (in
3132the form of an ISO) and install it in an automated manner.
3233
33- #### Casting
34+ #### Building
3435
35- Casting (or building) is the process that takes image sources and produces
36- a final goldboot image containing all customizations.
36+ Building is the process that takes image sources and produces a final goldboot
37+ image containing all customizations.
3738
3839Under the hood, foundries cast images by spawning a Qemu virtual machine and
3940running one or more image molds against it (via SSH or VNC). Once the virtual
@@ -51,18 +52,19 @@ fabricator runs shell commands on the image which can be useful in many cases.
5152
5253## Adding new operating systems
5354
54- If ` goldboot ` doesn't already support your operating system, it should be possible
55- to add it relatively easily.
55+ If ` goldboot ` doesn't already support your operating system, it should be
56+ possible to add it relatively easily.
5657
5758Start by finding an OS similar to yours in the ` goldboot::foundry::os ` module.
5859
5960TODO
6061
6162## OS maintenance
6263
63- OS support often need constant maintenance as new upstream releases are made and old
64- ones are retired. Typically this involves adding new versions and marking some
65- as deprecated, but occasionally upstream changes may cause breakages for us.
64+ OS support often need constant maintenance as new upstream releases are made and
65+ old ones are retired. Typically this involves adding new versions and marking
66+ some as deprecated, but occasionally upstream changes may cause breakages for
67+ us.
6668
6769For example, we have a struct that tracks Alpine releases which needs to be
6870updated about twice per year:
@@ -84,4 +86,5 @@ pub enum AlpineRelease {
8486```
8587
8688## Testing
89+
8790TODO
0 commit comments