From 4886e4cb3047bc4cf55ff7a47d97e73730bdcd64 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Julie=20Koubov=C3=A1?= Date: Thu, 21 Dec 2023 18:54:40 +0100 Subject: [PATCH 1/3] Update installation.md --- _docs/installation.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/_docs/installation.md b/_docs/installation.md index 0715081..f81f7bb 100644 --- a/_docs/installation.md +++ b/_docs/installation.md @@ -86,23 +86,27 @@ As a bit of a special case, Chimera also provides root file system tarballs. This is a small, pre-packaged Chimera installation. The following flavors are always available: -* Bootstrap tarballs (bootstrapped from the `base-bootstrap` metapackage) +* **Bootstrap tarballs** (created from the `base-bootstrap` metapackage) are suitable for setting up small containers that you can add more software into, e.g. with Docker. They only contain a bare userland - and `apk`. -* Minimal tarballs (bootstrapped from the `base-minimal` metapackage) are + and `apk`. They don't contain the init system suite or tools for building + an initfs, and won't boot without installing the `base-minimal` + metapackage and a kernel. + +* **Minimal tarballs** (created from the `base-minimal` metapackage) are suitable for setting up bare bootable systems. They do not contain a kernel or a bootloader, but they do contain an init system suite, - a `getty` and user management tools. -* Core tarballs (bootstrapped from `base-core` metapackage) are larger and - contain packages suitable for most deployments. Like minimal tarballs + a `getty`, and user management tools. + +* **Core tarballs** (created from the `base-core` metapackage) are larger and + contain packages suitable for most deployments. Like minimal tarballs, they do not contain a kernel or a bootloader, but they do contain - programs such as those for manipulating filesystems and networks. + programs for manipulating filesystems and networks, and more. They are handy for chroot-style installations that are fully manual, mostly to save time bootstrapping with `apk` from scratch. -In addition to this, tarball counterpart for every device-specific image +In addition to this, a tarball counterpart for every device-specific image is available. You can use these for manual installation on such devices, or you can create device images using Chimera's `mkimage.sh` using these. From 80659b2b8447041dee0ae6ca96a510436091118b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Julie=20Koubov=C3=A1?= Date: Thu, 21 Dec 2023 19:02:17 +0100 Subject: [PATCH 2/3] Update installation.md --- _docs/installation.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/_docs/installation.md b/_docs/installation.md index f81f7bb..99dffe0 100644 --- a/_docs/installation.md +++ b/_docs/installation.md @@ -86,19 +86,18 @@ As a bit of a special case, Chimera also provides root file system tarballs. This is a small, pre-packaged Chimera installation. The following flavors are always available: -* **Bootstrap tarballs** (created from the `base-bootstrap` metapackage) - are suitable for setting up small containers that you can add more - software into, e.g. with Docker. They only contain a bare userland +* **Bootstrap** tarballs (created from the `base-bootstrap` metapackage) + are suitable for containers (e.g., Docker). They only contain a bare userland and `apk`. They don't contain the init system suite or tools for building - an initfs, and won't boot without installing the `base-minimal` - metapackage and a kernel. + an initfs. They won't boot without installing the `base-minimal` metapackage, + a kernel, and a bootloader. -* **Minimal tarballs** (created from the `base-minimal` metapackage) are +* **Minimal** tarballs (created from the `base-minimal` metapackage) are suitable for setting up bare bootable systems. They do not contain a kernel or a bootloader, but they do contain an init system suite, a `getty`, and user management tools. -* **Core tarballs** (created from the `base-core` metapackage) are larger and +* **Core** tarballs (created from the `base-core` metapackage) are larger and contain packages suitable for most deployments. Like minimal tarballs, they do not contain a kernel or a bootloader, but they do contain programs for manipulating filesystems and networks, and more. @@ -113,7 +112,7 @@ or you can create device images using Chimera's `mkimage.sh` using these. ## Verifying system media In each media bundle, the `sha256sums.txt` file contains SHA256 checksums -of every file. Use this to check that your downloaded file is not corrupt. +of every file. Use this to check that your downloaded file is not corrupted. The `sha256sums.txt` file is signed with [minisign](https://jedisct1.github.io/minisign/). The signing key is unique for each release batch. You can use this to make From b2eaee4e1d04313d6e22b9e1d7296c43cd624e61 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Julie=20Koubov=C3=A1?= Date: Thu, 21 Dec 2023 19:06:36 +0100 Subject: [PATCH 3/3] Update installation.md --- _docs/installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/installation.md b/_docs/installation.md index 99dffe0..147c812 100644 --- a/_docs/installation.md +++ b/_docs/installation.md @@ -83,7 +83,7 @@ Do note that SD card images have the root filesystem journal disabled. ### Root filesystem tarballs As a bit of a special case, Chimera also provides root file system tarballs. -This is a small, pre-packaged Chimera installation. The following flavors +They are small, pre-packaged Chimera installations. The following flavors are always available: * **Bootstrap** tarballs (created from the `base-bootstrap` metapackage)