Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain tarballs more #22

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Explain tarballs more #22

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4886e4c
Update installation.md
juliekoubova Dec 21, 2023
80659b2
Update installation.md
juliekoubova Dec 21, 2023
b2eaee4
Update installation.md
juliekoubova Dec 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 15 additions & 12 deletions _docs/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,33 +83,36 @@ 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 (bootstrapped 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
* **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. They won't boot without installing the `base-minimal` metapackage,
a kernel, and a bootloader.

* **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.

## 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
Expand Down