Skip to content

Commit

Permalink
docs updates
Browse files Browse the repository at this point in the history
  • Loading branch information
q66 committed Oct 27, 2024
1 parent 2c21815 commit 017d581
Show file tree
Hide file tree
Showing 4 changed files with 23 additions and 20 deletions.
3 changes: 2 additions & 1 deletion _docs/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,8 @@ You will need the following:

In general, for a console-based system, you will need at least 128MB
or more RAM for the system to be truly usable. A graphical desktop will
need more, depending on the desktop (1GB is recommended for GNOME installs).
need more, depending on the desktop (1GB or more is recommended for
graphical installs).

OCI containers are available for `x86_64`, `ppc64e`, `aarch64` as well
as `riscv64` at `chimeralinux/chimera:latest`. They will run in any
Expand Down
14 changes: 4 additions & 10 deletions _docs/installation/boot.md
Original file line number Diff line number Diff line change
Expand Up @@ -152,7 +152,7 @@ login prompt (`getty`) for all consoles the kernel outputs to.

### Picking the boot option

Console images come with two boot options, regular boot and RAM
Images come with two boot options, regular boot and RAM
boot. The latter results in the whole system being copied to system
RAM, while the former will create a writable overlay over a read-only
mount.
Expand All @@ -162,15 +162,9 @@ you should be using the regular option. The benefit of the RAM option
is that the system will run faster, and especially for optical media,
will not result in accesses to the media.

Desktop images come with additional boot options to force console
boot (the default is to boot into GNOME desktop with Wayland). It
is also possible to force X11 by editing the graphical boot option
and adding the `nowayland` kernel command line parameter, but keep
in mind that GNOME currently has issues under X11 with most accelerated
drivers (software rendering works fine, so you may use it on systems
with unaccelerated 2D framebuffers) which may result in it freezing
on the first frame. Therefore, it is highly recommended to always
use Wayland for GNOME (X11 works for other window managers/desktops).
Desktop images will by default automatically boot into a desktop.
If you wish to boot into a console environment, edit the boot option
and add `nogui` to the kernel command line.

### Logging in

Expand Down
16 changes: 7 additions & 9 deletions _docs/installation/images.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ section: 2.2
## Live ISO images

Every ISO image comes in two flavors. You have the base image, and the
desktop image.
desktop images.

### Base images

Expand All @@ -19,16 +19,14 @@ final system will be like, but such setups also require more knowledge.
### Desktop images

Desktop images come with a full graphical environment. The official
desktop for Chimera is GNOME. There are other graphical environments
available in the repositories.
desktop for Chimera is GNOME. There are also images with KDE Plasma.
Other graphical environments are available in the repositories.

If you want a GNOME setup, you will want to use a desktop image. It
comes with a more complete environment including a web browser and
other basic software.
Note that any image can be used to install any desktop. The images
merely boot into that desktop for the live environment and a local
(non-network) installation will by default install it.

Desktop images by default boot into a Wayland environment. There is
a separate bootloader option if that does not work for you for some
reason.
Desktop images boot into a Wayland environment.

## Device images

Expand Down
10 changes: 10 additions & 0 deletions _docs/installation/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -164,6 +164,16 @@ After that, try again and there should be no more errors:
# apk upgrade --available
```

If you did a local installation, you will have the `base-live` package
installed in the target system. You can remove it with `apk del`, like:

```
# apk del base-live
```

It is recommended to do so. If you wish to retain any packages that it
installs, you can `apk add` them explicitly.

### Device base package

For devices that would use device images, a special base package
Expand Down

0 comments on commit 017d581

Please sign in to comment.