Alpine Linux - User contributions [en]

Upgrading Qt

2026-04-18T10:01:07Z

PureTryOut:

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 6.8.x to 6.9.x) upgrade:

* kwin (input in login managers)
* plasma-integration (for plasmashell)
* layer-shell-qt (for plasmashell)
* kguiaddons (for plasmashell)
* libkscreen (for display configuration)
* powerdevil (for power management KCM)
* pyside6 (all it's users need to be rebuild as well)

For QtWebengine:

* angelfish
* kaccounts-providers
* signon-ui

[[Category:Development]]
[[Category:System Administration]]

Upgrading Qt

2026-04-11T08:10:51Z

PureTryOut:

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 6.8.x to 6.9.x) upgrade:

* kwin (input in login managers)
* plasma-integration (for plasmashell)
* layer-shell-qt (for plasmashell)
* kguiaddons (for plasmashell)
* libkscreen (for display configuration)
* pyside6 (all it's users need to be rebuild as well)

For QtWebengine:

* angelfish
* kaccounts-providers
* signon-ui

[[Category:Development]]
[[Category:System Administration]]

Upgrading Qt

2025-07-13T09:39:13Z

PureTryOut:

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 6.8.x to 6.9.x) upgrade:

* plasma-integration
* kwin
* layer-shell-qt
* pyside6 (all it's users need to be rebuild as well)

For QtWebengine:

* angelfish
* kaccounts-providers
* signon-ui

Upgrading Qt

2025-07-10T21:21:59Z

PureTryOut:

Upgrading Qt

2025-07-10T18:58:55Z

PureTryOut:

Release Notes for Alpine 3.22.0

2024-12-05T15:39:04Z

PureTryOut:

As always, make sure to read [[Upgrading Alpine to a new major release]] when upgrading to a new release.

If you experience any issues with the upgrade, please let us know and file an issue in our repositories.

== Important changes ==

== Significant changes ==

The X11 session for KDE Plasma has been removed. If you had <code>plasma-workspace-x11</code> installed make sure to remove it from <code>/etc/apk/world</code>. Instead Wayland is the only available option now.

== Note-worthy updates ==

As always, a lot of packages were upgraded. Make sure to read the indivdual release notes of the projects you use.

* Linux TODO
* busybox TODO
* GCC TODO
* LLVM TODO
* Go TODO
* Rust TODO
* PHP TODO
* GNOME TODO
* KDE Plasma TODO
* LXQt TODO
* Qt TODO
* wlroots TODO

== Significant removals ==

Release Notes for Alpine 3.19.0

2023-12-03T19:11:34Z

PureTryOut: /* Upgrades */

== Base System ==

=== iptables-nft ===

The <code>/sbin/iptables{,-save,-restore}</code> symlinks now point to xtables-nft-multi instead of xtables-legacy-multi. This means they use the nftables kernel backend instead of the legacy iptables one.

Since the new iptables- binaries also don't use the iptables backend, to work with any existing rules and save them, you need to install {{pkg|iptables-legacy}} and use <code>iptables-legacy-save</code>.

Because mixing backends is not supported, you should reboot your system if you have to use the iptables commands after upgrading.

=== netns ===

The OpenRC package contains a patch to make it possible to start most services in netns namespaces. See also [[Netns|netns]].

== Others ==

=== HashiCorp packages ===

Due to [https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license the relicensing of HashiCorp software] to [https://spdx.org/licenses/BUSL-1.1.html BUSL-1.1], a non-Open-Source license, the following software have been removed from Alpine:

* Consul
* Nomad
* Packer
* Terraform
* Vault

Our discussion on the topic can be found [https://gitlab.alpinelinux.org/alpine/aports/-/issues/15193 here].

{{pkg|opentofu}}, a fork of Terraform, is available in our testing repository for users of our rolling release, edge.

=== Java 21 ===

The latest LTS java release, openjdk21, is now available in the community repository.

=== KDE ===

KDE Applications have been upgraded from 23.04.x to 23.08.x. KDE Frameworks have been upgraded from 5.105.0 to 5.112.0.
Note that the KDE Frameworks packages have been renamed to add a 5 suffix in preparation for the upcoming KDE 6 release in the next Alpine release. Everything should automatically be upgraded properly but if problems occur make sure to check if the right renamed packages are installed.

=== Yggdrasil v0.5 ===

{{pkg|yggdrasil}} was upgraded to 0.5.x and the new routing scheme is incompatible with previous versions. "Nodes running this new version '''will not''' be able to peer with earlier versions of Yggdrasil" ([https://github.com/yggdrasil-network/yggdrasil-go/releases/tag/v0.5.0 v0.5.0 release notes], [https://yggdrasil-network.github.io/2023/10/22/upcoming-v05-release.html v0.5 blog post]).

== Upgrades ==

* GCC 13
* LLVM 17
* Kea 2.4
* Xen 4.18
* Git 2.43
* Perl 5.38
* PHP 8.3
* PostgreSQL 16
* SQLite 3.44
* Redis 7.2
* Node.js (lts) 20.10
* Node.js (current) 21.2
* QEMU 8.1
* Ceph 18.2
* GNOME 45
* LXQt 1.4
* wlroots 0.17
* Go 1.21
* Rust 1.72
* Crystal 1.10
* Racket 8.11
* ECL 23.9.9
* Erlang 26
* zlib 1.3
* libsodium 1.0.19
* ICU 74.1
* Protobuf 24.4
* fmt 10
* PipeWire 1.0.0

[[Category:News]]

Release Notes for Alpine 3.19.0

2023-11-21T08:02:04Z

PureTryOut: /* Others */

Release Notes for Alpine 3.18.0

2023-05-08T09:53:43Z

PureTryOut:

=== Linux Kernel ===

linux-lts 6.1 https://lkml.org/lkml/2022/12/11/206

Kernel modules are now signed.

=== musl 1.2.4 ===

Support for DNS lookups over TCP.

https://www.openwall.com/lists/musl/2023/05/02/1

=== DT_RELR ===

on x86, x86_64, and ppc64le, <code>-Wl,-z,pack-relative-relocs</code> is now added to the base LDFLAGS. this reduces elf (executable/shared-library) size by 10% on average.

however, these binaries are now not portable to other musl-based systems that have a musl older than 1.2.4, because older versions are incapable of loading these binaries.

=== GNOME ===

The gnome metapackage was reworked and the packages gnome-apps-extra and gnome-games-collection were removed to avoid opinionated lists in metapackages. It is advised to remove those from /etc/apk/world before performing the upgrade. Additionally, the new subpackage gnome-dev-tools was added following upstream's recommendations.

=== Plasma 5.27.4 ===

From 5.26.5 before. This includes some new packages like plasma-welcome (a welcoming application that shows up on first boot to configure some initial settings) and flatpak-kcm (a configuration page for the system settings to control Flatpak permissions, much like GNOME's Flatseal).
This Plasma release is the last one that will be build on Qt5 and will probably remain in use for Alpine 3.19 as well.

=== dbus ===

dbus-activation has been removed from packages <code>openrc-settingsd</code> and <code>apk-polkit-rs</code>. To make use of their services, make sure to start and enable the <code>openrc-settingsd</code> and <code>apk-polkit-server</code> services, respectively.

=== removal of pipewire-media-session ===

pipewire-media-session was removed, as upstream explicitly recommends to not use it, and it's completely superceded by wireplumber.
if you used it, make sure you don't have pipewire-media-session in /etc/apk/world, and configure any scripts you might've had to launch wireplumber instead.

=== Python ===

python 3.11 https://docs.python.org/3/whatsnew/3.11.html

=== splitting of python pycache .pyc files ===

most python modules split their __pycache__ to a -pyc subpackage, pulled by default. to save space and not pull it (incurring python interpreter startup costs, as it generates it each run), run <code>apk add !python3-pyc</code>

=== PHP 8.2 ===

Added 8.2 packages with subset of the most common extensions. Version 8.1 still remains primary provider priority but some web applications started to use 8.2.

=== Ruby 3.2 ===

Ruby was updated to 3.2. https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/

=== gdk-pixbuf-loaders ===

a few gdk-pixbuf loaders were added, and they were all added to an install_if metapackage rule- <code>apk add gdk-pixbuf-loaders</code> to enable the loaders for corresponding image libraries you have installed.

=== Docker 23 ===

The <code>docker</code> package shipped with Alpine 3.18 has a dependency on <code>docker-cli-buildx</code>, as Docker 23 now uses it for builds.

Also, Docker 23 no longer enables the <code>overlay</code> storage driver, as it has been deprecated for a long time and is nearing removal. if your deployment is still configured to use it, <code>dockerd</code> will fail to start. To fix this, either...

* migrate to <code>overlay2</code> in <code>/etc/docker/daemon.json</code>
* hardcode it to <code>overlay</code> in the same file (instead of blank), though this will eventually break in a future upgrade

For more detailed information about Docker 23, please refer to https://docs.docker.com/engine/release-notes/23.0/

Release Notes for Alpine 3.16.0

2022-05-02T12:32:06Z

PureTryOut:

== Important changes ==

=== /tmp mounted as tmpfs ===

Previously <code>/tmp</code> was just part of the root filesystem and was cleaned on boot via the bootmisc openrc service script. In v3.16, on new installation, <code>/tmp</code> will be mounted as tmpfs.

== New features and noteworthy new packages ==

=== KDE ===

Plasma has been upgraded from 5.23 to 5.24.

KDE applications (the release service) have been upgraded from 21.08 to 22.04 and KDE Frameworks have been upgraded from 5.88 to 5.93.

Plasma Mobile Gear have been upgraded from 21.12 to 22.04.

Release Notes for Alpine 3.15.0

2021-11-25T18:38:18Z

PureTryOut: Add details about Pipewire changes

== Important changes ==

=== New package signing keys ===

New signing keys have been generated for v3.15 ongoing. The key size has been increased from 2048 bits to 4096 bits. Make sure you have <code>alpine-keys-2.4-r0</code> or later before upgrading to 3.15 (or downgrading from edge).

=== MIPS64 discontinued ===

The build hardware we use for building the packages is broken and the architecture is EOL, so there is no new hardware available anymore. As a consequence, there will be no v3.15 release for mips64, and existing releases can no longer receive security updates, so continued use of this architecture is not recommended.

=== radvd no longer enables ipv6 forwarding ===

The radvd init script no longer enables ipv6 forwarding. To enable ipv6 forwarding (necessary for most networks), add <code>net.ipv6.conf.all.forwarding=1</code> to {{path|/etc/sysctl.conf}} or to a file in {{path|/etc/sysctl.d}}.

=== Move from sudo to doas ===

doas is the default temporary privilege escalation tool. You are advised to migrate from sudo to doas as 3.15 will be the last release to support sudo throughout its full lifecycle, in 3.16 sudo will be moved from main to community.

=== PipeWire doesn't auto-start a session manager anymore ===

In 3.14 and earlier the PipeWire default config was edited in packaging to auto-start pipewire-media-session as the default session manager. Since we now have wireplumber available as an alternative session manager, this has been changed in favor of a launch wrapper for pipewire at <code>/usr/libexec/pipewire-launcher</code>. When executed this will launch pipewire, pipewire-media-session or wireplumber, and pipewire-pulse, depending on what modules are available. If you were launching <code>/usr/bin/pipewire</code> and the session manager manually before, please use the new launcher wrapper instead. WirePlumber can now also be used as a proper alternative for pipewire-media-session.

== New features and noteworthy new packages ==

=== Compressed kernel modules ===

Kernel modules are now compressed using gzip.

=== UEFI Secure Boot ===

Complete support for [[UEFI Secure Boot]] realized by package {{pkg|secureboot-hook}} and {{pkg|efi-mkkeys}}.

=== Support overlaytmpfs mount options ===

It is now possible to use tmpfs(5) mount options with <code> overlaytmpfsflags</code>, when using <code>overlaytmpfs</code>, see mkinitfs-bootparams(7). Also, <code>rootflags</code> and <code>rootfstype</code> options are now picked up for the underlying rootfs mount.

=== Support for out-of-tree kernel modules built from source ===

Alpine Kernel Module Support ({{pkg|akms}}) – support for building out-of-tree Linux kernel modules from source in an automated and organized fashion. It’s like DKMS, but designed specifically for Alpine Linux.

=== PostgreSQL multiple major versions ===

PostgreSQL packaging has been reworked to allow multiple major versions of PostgreSQL server to be installed side by side. This makes it possible to allow to upgrade PostgreSQL cluster from one major version to the next using <code>pg_upgrade</code> tool, and also to run an older major version of PostgreSQL on the latest version of Alpine Linux. The latest PostgreSQL version can be installed simply with <code>apk add postgresql</code> as before. If you need an older major version, install the specific package, e.g. {{pkg|postgresql13}}. You can switch between installed major versions using command <code>pg_versions</code>.

See [https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/27275 MR #27275] for more information.

=== Rofi for Wayland ===

Rofi can now be used on Wayland desktops thanks to the fork {{pkg|rofi-wayland}}.

=== Encrypted Data Disk and System Disk modes ===

<code>setup-disk</code> ({{pkg|alpine-conf}}) now supports encrypted Data Disk and System Disk modes.

== Significant updates ==

=== 5.15 LTS kernels ===

linux-lts and linux-virt upgraded to 5.15

'''Note:''' If you are using ''ZFS'' and depend on symlinks under /dev/zvol/ some are sporadically not created during boot, this is known upstream by ''OpenZFS'' and we track the issue [https://gitlab.alpinelinux.org/alpine/aports/-/issues/13198 here].

=== Ruby 3.0.2 ===

Ruby has been upgraded to version 3.0.2.

Packages {{pkg|ruby-minitest}}, {{pkg|ruby-net-telnet}}, {{pkg|ruby-power_assert}}, {{pkg|ruby-sdbm}}, {{pkg|ruby-test-unit}}, {{pkg|ruby-xmlrpc}}, {{pkg|ruby-webrick}} has been moved from ruby aport to separate aports. Please note that since they don’t inherit the version from the ruby aport anymore, their new (real) version is ''lower'' than before!

Subpackages ruby-bigdecimal, ruby-etc, ruby-fiddle, ruby-gdbm, ruby-io-console, ruby-irb, and ruby-json have been merged into ruby-libs.

=== LLVM12 added ===

LLVM12 is now available.

=== KDE ===

KDE Plasma has been upgraded to version 5.23, and KDE Applications have been upgraded to 21.08.
Plasma Mobile Gear has been upgraded to 21.10.

=== Node.js ===

Node.js (LTS) has been upgraded to version 16.13.0. nodejs-current has been upgraded to 17.0.1.

=== PHP ===

PHP 7.4 started to phase out (1 year of security support left).
Transition to 8.0 is not finished yet as some app still require old version.

=== PostgreSQL 14 ===

PostgreSQL has been upgraded to version 14.0. Since this release, multiple major versions are provided, currently: 12, 13, and 14.

Support for Just-in-time compilation (JIT) has been moved into subpackage {{pkg|postgresql-jit}}.

{{pkg|libpq}} is now built without LDAP support which reduces number of installed dependencies. Note that this does ''not'' affect the LDAP support in PostgreSQL server, it’s preserved.

=== Mercurial ===

mercurial has been upgraded to 5.9.3

=== Dlang build tools (DMD, DUB, LDC) have been updated ===

Both compilers have been updated to frontend version v2.098.0 (LDC equivalent: v1.28.0).
Dub has been updated to v1.27.0.
LDC now always uses `--export-dynamic` so that code compiled without debug infos (`-g`) will still have the function name in its stack trace.

=== OpenJDK 17 added ===

The latest OpenJDK LTS version (17) has been added to this release and is available via the community repository.

=== GNOME 41 ===

Most GNOME packages have been upgraded to version 41.

=== Crystal ===

{{pkg|crystal}} has been upgraded to version 1.2.2.

=== Kea ===

{{pkg|kea}} has been upgraded to version 2.0.0.

=== OpenLDAP ===

{{pkg|openldap}} has been upgraded to version 2.6.0.

=== Rust ===

{{pkg|rust}} has been upgraded to version 1.56.1.

== Significant removals ==

=== QtWebKit was removed due to lack of upstream support ===

qt5-qtwebkit, kdewebkit, wkhtmltopdf, and py3-pdfkit have been removed due to known vulnerabilities and lack of upstream support for qtwebkit. Other programs have been adjusted to use qt5-qtwebengine where appropriate. The most direct replacement for wkhtmltopdf is weasyprint, which is available in the Alpine Linux community repository. puppeteer and pandoc are also options, depending on your needs. See [https://gitlab.alpinelinux.org/alpine/aports/-/issues/12888 #12888] for more information.

== Development-related changes ==

=== PostgreSQL ===

{{pkg|postgresql-dev}} has been split into {{pkg|libpq-dev}}, {{pkg|libecpg-dev}}, and <code>postgresql-dev</code> (this is ''provided'' by {{pkg|postgresql14-dev}}, {{pkg|postgresql13-dev}} etc.). Basically, only PostgreSQL extensions should use {{pkg|postgresql-dev}} in <code>makedepends</code>; all other aports should use {{pkg|libpq-dev}} and/or {{pkg|libecpg-dev}} (there are some exceptions though).

PostgreSQL extensions (typically packages with <code>postgresql-</code> prefix) should use {{pkg|postgresql-dev}} in <code>makedepends</code> – this will install the latest <code>postgresql<majorver>-dev</code> package, unless there’s a dependency on a specific postgresql version in the dependency graph (which shouldn’t be).

Each aport providing a PostgreSQL extension must explicitly depend on specific <code>postgresql<majorver></code> package, not <code>postgresql</code> provider. This should be solved by adding the following into the <code>package</code> function (!) in each aport that provides PostgreSQL extension:

<pre>
depends="postgresql$(pg_config --major-version)"
</pre>

Release Notes for Alpine 3.15.0

2021-10-19T11:22:49Z

PureTryOut:

== aports ==

=== QtWebKit was removed due to lack of upstream support ===

qt5-qtwebkit, kdewebkit, wkhtmltopdf, and py3-pdfkit have been removed due to known vulnerabilities and lack of upstream support for qtwebkit. Other programs have been adjusted to use qt5-qtwebengine where appropriate. The most direct replacement for wkhtmltopdf is weasyprint, which is available in the Alpine Linux community repository. puppeteer and pandoc are also options, depending on your needs. See [https://gitlab.alpinelinux.org/alpine/aports/-/issues/12888 #12888] for more information.

=== radvd no longer enables ipv6 forwarding ===

The radvd init script no longer enables ipv6 forwarding. To enable ipv6 forwarding (necessary for most networks), add <code>net.ipv6.conf.all.forwarding=1</code> to {{path|/etc/sysctl.conf}} or to a file in {{path|/etc/sysctl.d}}.

=== OpenSSL 3.0 ===

openssl has been upgraded to 3.0. In addition to the changes at https://wiki.openssl.org/index.php/OpenSSL_3.0, note that this release effectively disables TLS 1.0 and TLS 1.1 by default: https://github.com/openssl/openssl/commit/aba03ae571ea677fc484daef00a21ca8f7e82708.

=== New package signing keys ===

New signing keys have been generated for v3.15 ongoing. The key size has been increased from 2048 bits to 4096 bits. Make sure you have <code>alpine-keys-2.4-r0</code> or later before upgrading to 3.15 (or downgrading from edge).

=== Ruby 3.0 ===

Ruby has been upgraded to version 3.0.

=== LLVM12 added ===

LLVM12 is now available.

=== KDE ===

KDE Plasma has been upgraded to version 5.23, and KDE Applications have been upgraded to 21.08.
Plasma Mobile Gear has been upgraded to 21.10.

Bluetooth audio

2021-09-28T07:25:44Z

PureTryOut: /* PulseAudio */

== PulseAudio ==

Before you can connect your device to Bluetooth speakers or headphones, you'll have to make sure {{Pkg|pulseaudio-bluez}} is installed.

== PipeWire ==

For PipeWire you need to install {{Pkg|pipewire-spa-bluez}}.

PipeWire

2021-08-03T08:44:58Z

PureTryOut: /* Audio Group */

{{Draft|The instructions below have not been thoroughly tested and may break things.}}

[https://pipewire.org/ PipeWire] is a multimedia processing engine that aims to improve audio and video handling on Linux.

== Prerequisites ==

=== Audio Group ===

When elogind is not available, the user has to be added to the <code>audio</code> group. The user must log in for this to take effect.

<pre>
# addgroup audio <user>
</pre>

=== D-Bus ===

PipeWire requires a running [https://www.freedesktop.org/wiki/Software/dbus/ D-Bus] session. If you use a full desktop environment this will probably be started automatically, but with minimal window managers it must be done manually.

<pre>
# apk add dbus dbus-openrc dbus-x11
# rc-service dbus start
# rc-update add dbus default
</pre>

Then use <code>dbus-launch</code> whenever you start an X or Wayland session. For example:
<pre>
$ dbus-launch --exit-with-session sway
</pre>

=== XDG_RUNTIME_DIR ===

If you are not using a Desktop Manager, ensure that your <code>XDG_RUNTIME_DIR</code> is set to a user-writable location. By default for pulseaudio this is <code>/run/user/1000/</code> or <code>/tmp</code>. If this is not set, pipewire will create a directory in your home folder instead, called <code>~/pulse</code>, and on attempting to run Pavucontrol or pactl, you will get the following error:

<pre>
$ pactl list
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
</pre>

== Installation and configuration ==

<pre>
# apk add pipewire
</pre>

Create custom configuration file in <code>/etc/pipewire/pipewire.conf</code>:

<pre>
# mkdir /etc/pipewire
# cp /usr/share/pipewire/pipewire.conf /etc/pipewire/
</pre>

Uncomment the following line in <code>/etc/pipewire/pipewire.conf</code>:

<pre>
{ path = "/usr/bin/pipewire-media-session" args = "" }
</pre>

Enable the <code>snd_seq</code> kernel module for ALSA support.

<pre>
# modprobe snd_seq
# echo snd_seq >> /etc/modules
</pre>

=== ALSA ===

If you used neither Jack or PulseAudio nor intend to.

<pre>
# touch /etc/pipewire/media-session.d/with-alsa
</pre>

=== PulseAudio ===

PipeWire can run a [https://www.freedesktop.org/wiki/Software/PulseAudio/ PulseAudio] daemon which should allow all existing PulseAudio applications to be used with the PipeWire backend.

<pre>
# apk add pipewire-pulse
</pre>

It should be automatically enabled.

=== JACK ===

If you will be using PipeWire for [https://jackaudio.org/ JACK] applications install the required package and make system wide links to the PipeWire replacement JACK libraries (I have not had success using <code>pw-jack</code>). You will not need to start a JACK server.

<pre>
# apk add pipewire-jack
# ln -sf /usr/lib/pipewire-0.3/jack/libjackserver.so.0 /usr/lib/libjackserver.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjacknet.so.0 /usr/lib/libjacknet.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjack.so.0 /usr/lib/libjack.so.0
</pre>

{{Note|These symlinks might be overwritten during updates.}}

=== Video ===

Video should work out-of-the-box with v4l2 devices (e.g. a lot of webcams) and [https://gstreamer.freedesktop.org/ GStreamer] applications.

=== Screen sharing on Wayland ===

You will need the right [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] backend for your desktop environment. Screen sharing is known to work on:
* GNOME with <code>xdg-desktop-portal-gtk</code>
* KDE Plasma with <code>xdg-desktop-portal-kde</code> and Firefox
* Sway with <code>xdg-desktop-portal-wlr</code> and Firefox

== Usage ==

Start the PipeWire media server. You'll probably get quite a few errors but just ignore them for now.

<pre>
$ pipewire
</pre>

In a different terminal window check the default output device. I don't yet know how this default can be changed for all applications, so you'd better hope it's right!

<pre>
$ pw-cat -p --list-targets
</pre>

Test sound is working using an audio file in a format supported by [http://www.mega-nerd.com/libsndfile/ libsndfile] (e.g. flac, opus, ogg, wav).

<pre>
$ pw-cat -p test.flac
</pre>

If you have a microphone test recording audio is working.

<pre>
$ pw-cat -r --list-targets
$ pw-cat -r recording.flac
(Speak for a while then stop it with Ctrl+c)
$ pw-cat -p recording.flac
</pre>

Test PulseAudio clients using a media player (most use PulseAudio) and if you use JACK test that too:

<pre>
# apk add jack-example-clients
$ jack_simple_client
</pre>

You should hear a sustained beep.

If you are happy everything is working, make PipeWire start automatically when your X or Wayland session starts. For example, you could add the <code>pipewire</code> command to <code>~/.xinitrc</code> or your window manager's config file.

== See Also ==

* [https://gitlab.freedesktop.org/pipewire/pipewire PipeWire source repository]
* [https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home PipeWire Wiki]
* [https://wiki.archlinux.org/index.php/PipeWire PipeWire on the ArchWiki]
* [https://wiki.gentoo.org/wiki/Pipewire PipeWire on the Gentoo Wiki]

[[Category:Multimedia]]

PipeWire

2021-07-31T18:25:28Z

PureTryOut: /* PulseAudio */

{{Draft|The instructions below have not been thoroughly tested and may break things.}}

[https://pipewire.org/ PipeWire] is a multimedia processing engine that aims to improve audio and video handling on Linux.

== Prerequisites ==

=== Audio Group ===

Add your normal user to the <code>audio</code> group. The user must log in for this to take effect.

<pre>
# addgroup audio <user>
</pre>

=== D-Bus ===

PipeWire requires a running [https://www.freedesktop.org/wiki/Software/dbus/ D-Bus] session. If you use a full desktop environment this will probably be started automatically, but with minimal window managers it must be done manually.

<pre>
# apk add dbus dbus-openrc dbus-x11
# rc-service dbus start
# rc-update add dbus default
</pre>

Then use <code>dbus-launch</code> whenever you start an X or Wayland session. For example:
<pre>
$ dbus-launch --exit-with-session sway
</pre>

=== XDG_RUNTIME_DIR ===

If you are not using a Desktop Manager, ensure that your <code>XDG_RUNTIME_DIR</code> is set to a user-writable location. By default for pulseaudio this is <code>/run/user/1000/</code> or <code>/tmp</code>. If this is not set, pipewire will create a directory in your home folder instead, called <code>~/pulse</code>, and on attempting to run Pavucontrol or pactl, you will get the following error:

<pre>
$ pactl list
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
</pre>

== Installation and configuration ==

<pre>
# apk add pipewire
</pre>

Create custom configuration file in <code>/etc/pipewire/pipewire.conf</code>:

<pre>
# mkdir /etc/pipewire
# cp /usr/share/pipewire/pipewire.conf /etc/pipewire/
</pre>

Uncomment the following line in <code>/etc/pipewire/pipewire.conf</code>:

<pre>
{ path = "/usr/bin/pipewire-media-session" args = "" }
</pre>

Enable the <code>snd_seq</code> kernel module for ALSA support.

<pre>
# modprobe snd_seq
# echo snd_seq >> /etc/modules
</pre>

=== ALSA ===

If you used neither Jack or PulseAudio nor intend to.

<pre>
# touch /etc/pipewire/media-session.d/with-alsa
</pre>

=== PulseAudio ===

PipeWire can run a [https://www.freedesktop.org/wiki/Software/PulseAudio/ PulseAudio] daemon which should allow all existing PulseAudio applications to be used with the PipeWire backend.

<pre>
# apk add pipewire-pulse
</pre>

It should be automatically enabled.

=== JACK ===

If you will be using PipeWire for [https://jackaudio.org/ JACK] applications install the required package and make system wide links to the PipeWire replacement JACK libraries (I have not had success using <code>pw-jack</code>). You will not need to start a JACK server.

<pre>
# apk add pipewire-jack
# ln -sf /usr/lib/pipewire-0.3/jack/libjackserver.so.0 /usr/lib/libjackserver.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjacknet.so.0 /usr/lib/libjacknet.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjack.so.0 /usr/lib/libjack.so.0
</pre>

{{Note|These symlinks might be overwritten during updates.}}

=== Video ===

Video should work out-of-the-box with v4l2 devices (e.g. a lot of webcams) and [https://gstreamer.freedesktop.org/ GStreamer] applications.

=== Screen sharing on Wayland ===

You will need the right [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] backend for your desktop environment. Screen sharing is known to work on:
* GNOME with <code>xdg-desktop-portal-gtk</code>
* KDE Plasma with <code>xdg-desktop-portal-kde</code> and Firefox
* Sway with <code>xdg-desktop-portal-wlr</code> and Firefox

== Usage ==

Start the PipeWire media server. You'll probably get quite a few errors but just ignore them for now.

<pre>
$ pipewire
</pre>

In a different terminal window check the default output device. I don't yet know how this default can be changed for all applications, so you'd better hope it's right!

<pre>
$ pw-cat -p --list-targets
</pre>

Test sound is working using an audio file in a format supported by [http://www.mega-nerd.com/libsndfile/ libsndfile] (e.g. flac, opus, ogg, wav).

<pre>
$ pw-cat -p test.flac
</pre>

If you have a microphone test recording audio is working.

<pre>
$ pw-cat -r --list-targets
$ pw-cat -r recording.flac
(Speak for a while then stop it with Ctrl+c)
$ pw-cat -p recording.flac
</pre>

Test PulseAudio clients using a media player (most use PulseAudio) and if you use JACK test that too:

<pre>
# apk add jack-example-clients
$ jack_simple_client
</pre>

You should hear a sustained beep.

If you are happy everything is working, make PipeWire start automatically when your X or Wayland session starts. For example, you could add the <code>pipewire</code> command to <code>~/.xinitrc</code> or your window manager's config file.

== See Also ==

* [https://gitlab.freedesktop.org/pipewire/pipewire PipeWire source repository]
* [https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home PipeWire Wiki]
* [https://wiki.archlinux.org/index.php/PipeWire PipeWire on the ArchWiki]
* [https://wiki.gentoo.org/wiki/Pipewire PipeWire on the Gentoo Wiki]

[[Category:Multimedia]]

KDE

2021-06-17T09:10:25Z

PureTryOut: /* Using a display manager */

{{TOC right}}

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

Note that the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. The rest of Plasma can however be installed separately to get a functional desktop.

= Installation =

=== Prerequisites ===

* [[Installation|Alpine Installation]]
* [[Setting_up_a_new_user#Creating_a_new_user|Create user accounts]]
* [[Alpine_setup_scripts#setup-xorg-base|Graphical base environment]]
* [[Enable_Community_Repository#Using_community_repositories|Enabled "community" repository]]

=== Plasma ===

Install the {{Pkg|plasma}} meta-package. This will install the required Plasma packages and {{Pkg|sddm}} and pre-configure it to use the Breeze theme.

Alternatively, a more minimal installation can be done by installing {{Pkg|plasma-desktop}}.

=== KDE Applications ===

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a more limited set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

= Starting Plasma =

Plasma can be started using a display manager or from the console.

=== Using a display manager ===

When Plasma is installed via the {{Pkg|plasma}} meta-package, this has already been setup using {{Pkg|sddm}}.

Make sure you enable and start the SDDM service.

<pre>
rc-update add sddm
rc-service start sddm
</pre>

* Select ''Plasma'' to launch a new session in Wayland
* Select ''Plasma (X11)'' to launch a new session in Xorg

=== From the console ===

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startplasma-x11</code> to your <code>.xinitrc</code> file. Then just start X.
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
</pre>

=See also=
* [[Flatpak]]

[[category:Desktop]]

Steam

2021-02-16T11:07:37Z

PureTryOut:

[http://store.steampowered.com/about/ Steam] is a popular game distribution platform by Valve.

{{Note|Steam for Linux only supports Ubuntu LTS. Thus, do not turn to Valve for support for issues with Steam on Alpine Linux.}}

== Installation ==

Steam requires glibc to run, and thus doesn't straight up run on Alpine Linux.
To work around this problem, we'll use [https://wiki.alpinelinux.org/wiki/Flatpak Flatpak].
Make sure you have the Flathub repository installed.

# apk add flatpak
$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
$ flatpak install com.valvesoftware.Steam

After installation Steam can be started using it's .desktop file or on the command line:

$ flatpak run com.valvesoftware.Steam

== Troubleshooting ==

=== My controllers aren't detected ===

By default Steam doesn't have permission to read your controllers.
This can be fixed by installing an udev rule from the official Steam package, but the udev rules are also available as an Alpine package.

# apk add steam-devices

=== SteamVR won't launch ===

Out of the box SteamVR might not be able to launch and give you various errors. Steam tries to fix this itself by setting the right capabilities on the SteamVR binary, but this doesn't work in the Flatpak. Instead we'll have do it manually.

# setcap CAP_SYS_NICE+ep ~/.var/app/com.valvesoftware.Steam/data/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher

Then restart Steam.

There is an issue for this [https://github.com/flathub/com.valvesoftware.Steam/issues/636#issuecomment-779763326 on the Flathub repository].

Steam

2021-02-16T10:55:39Z

PureTryOut:

Software management

2021-02-16T10:47:26Z

PureTryOut:

If you want to run [https://www.gnu.org/software/libc/ glibc] programs in Alpine Linux, there are a few ways of doing so. You could install glibc as additional to [https://musl.libc.org/ musl] (you would have to do this manually), or you could do it the easy way and use either Flatpak (the easiest) or a chroot. 

Because there are different use cases, this is just a slight overview about what's possible and what's intelligent. 

= Your options =

== Flatpak ==

Flatpak is by far the easiest method of running any graphical glibc program on Alpine.
Firstly install it.

sudo apk add flatpak

Then you can run any Flatpak application:

flatpak run <flatpak name>

It is recommended to enable [https://flathub.org Flathub] using it's instructions [https://flatpak.org/setup/Alpine/ here], as most glibc programs you might need will be packaged there.

You can then install applications from it, for example:

flatpak install com.valvesoftware.Steam

== Chroot ==

=== Gentoo Linux ===

Select a stage3 from [https://www.gentoo.org/downloads/ here] and portage latest from [https://www.gentoo.org/downloads/mirrors/ here] at gentoo/snapshots/portage-latest.tar.xz.

First,

sudo apk add xz

Enter the chroot:
mkdir ~/chroot
cd ~/chroot
tar -xvf stage3-*.tar.xz
tar -xvf portage-latest.tar.xz
mv portage usr
sudo mount --bind /dev dev
sudo mount --bind /sys sys
sudo mount -t proc proc proc
cp /etc/resolv.conf etc
sudo chroot . /bin/bash

And voilà, you have your working Gentoo chroot! 

You can now take a look at [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo's Handbook] to find out how you can configure and install your system, or simply extract/copy the program you need to run in your chroot enviroment and execute it.

Here is a wrapper script that is similar to <code>arch-chroot</code> when you frequently reuse this chroot:

Also, create an account with the same user name as host current user to the chroot or make changes to the userspec option to chroot line.

{{Cat|gentoo-chroot.sh|<nowiki>!/bin/bash
CHROOT_PATH="/home/$USER/chroot"
cd $CHROOT_PATH
mount | grep $CHROOT_PATH/dev || sudo mount --bind /dev dev
mount | grep $CHROOT_PATH/sys || sudo mount --bind /sys sys
mount | grep $CHROOT_PATH/proc || sudo mount -t proc proc proc
cp /etc/resolv.conf etc
sudo chroot --userspec=$USER:users . /bin/bash
echo "You must manually unmount $CHROOT_PATH/dev, $CHROOT_PATH/sys, $CHROOT_PATH/proc."
</nowiki>
}}

Do at <code>chmod +x gentoo-chroot.sh</code> to get it to work.

=== Arch Linux ===

Either use '''pacstrap''' (included with the arch-install-scripts package) or an Arch bootstrap image:

sudo apk add arch-install-scripts
mkdir ~/chroot && cd ~/chroot
curl -O https://mirrors.edge.kernel.org/archlinux/iso/latest/archlinux-bootstrap-2019.02.01-x86_64.tar.gz
sudo tar xzf archlinux-bootstrap-2019.02.01-x86_64.tar.gz && rm archlinux-bootstrap-2019.02.01-x86_64.tar.gz
sudo sed -i '/evowise/s/^#//' root.x86_64/etc/pacman.d/mirrorlist
sudo sed -i '/CheckSpace/s/^/#/' root.x86_64/etc/pacman.conf
sudo arch-chroot root.x86_64
[chroot]# pacman-key --init
[chroot]# pacman-key --populate archlinux

Once that is done, update the system and install the desired package(s) (denoted by ''"foo"'' in this example):

[chroot]# pacman -Syu ''foo''

=== Debian ===

Use the provided debootstrap package to create the Debian chroot. <code>--arch</code> is optional, depending of your needs.

On the '''linux-grsec''' kernel, you will need to relax chroot limitations:

sudo apk add debootstrap
for i in /proc/sys/kernel/grsecurity/chroot_*; do echo 0 | sudo tee $i; done
mkdir ~/chroot
sudo debootstrap --arch=i386 wheezy ~/chroot http://http.debian.net/debian/
for i in /proc/sys/kernel/grsecurity/chroot_*; do echo 1 | sudo tee $i; done
sudo chroot ~/chroot /bin/bash

You can now use <code>apt-get</code> to install needed packages.

[[Category:Development]]
[[Category:Installation]]

Software management

2021-02-16T10:45:15Z

PureTryOut:

{{Draft}}

If you want to run [https://www.gnu.org/software/libc/ glibc] programs in Alpine Linux, there are a few ways of doing so. You could install glibc as additional to [https://musl.libc.org/ musl] (you would have to do this manually), or you could do it the easy way and use either Flatpak (the easiest) or a chroot. 

Because there are different use cases, this is just a slight overview about what's possible and what's intelligent. 

= Your options =

== Flatpak ==

Flatpak is by far the easiest method of running any graphical glibc program on Alpine.
Firstly install it.

sudo apk add flatpak

Then you can run any Flatpak application:

flatpak run <flatpak name>

It is recommended to enable [https://flathub.org Flathub] using it's instructions [https://flatpak.org/setup/Alpine/ here], as most glibc programs you might need will be packaged there.

You can then install applications from it, for example:

flatpak install com.valvesoftware.Steam

== Chroot ==

=== Gentoo Linux ===

Select a stage3 from [https://www.gentoo.org/downloads/ here] and portage latest from [https://www.gentoo.org/downloads/mirrors/ here] at gentoo/snapshots/portage-latest.tar.xz.

First,

sudo apk add xz

Enter the chroot:
mkdir ~/chroot
cd ~/chroot
tar -xvf stage3-*.tar.xz
tar -xvf portage-latest.tar.xz
mv portage usr
sudo mount --bind /dev dev
sudo mount --bind /sys sys
sudo mount -t proc proc proc
cp /etc/resolv.conf etc
sudo chroot . /bin/bash

And voilà, you have your working Gentoo chroot! 

You can now take a look at [https://wiki.gentoo.org/wiki/Handbook:Main_Page Gentoo's Handbook] to find out how you can configure and install your system, or simply extract/copy the program you need to run in your chroot enviroment and execute it.

Here is a wrapper script that is similar to <code>arch-chroot</code> when you frequently reuse this chroot:

Also, create an account with the same user name as host current user to the chroot or make changes to the userspec option to chroot line.

{{Cat|gentoo-chroot.sh|<nowiki>!/bin/bash
CHROOT_PATH="/home/$USER/chroot"
cd $CHROOT_PATH
mount | grep $CHROOT_PATH/dev || sudo mount --bind /dev dev
mount | grep $CHROOT_PATH/sys || sudo mount --bind /sys sys
mount | grep $CHROOT_PATH/proc || sudo mount -t proc proc proc
cp /etc/resolv.conf etc
sudo chroot --userspec=$USER:users . /bin/bash
echo "You must manually unmount $CHROOT_PATH/dev, $CHROOT_PATH/sys, $CHROOT_PATH/proc."
</nowiki>
}}

Do at <code>chmod +x gentoo-chroot.sh</code> to get it to work.

=== Arch Linux ===

Either use '''pacstrap''' (included with the arch-install-scripts package) or an Arch bootstrap image:

sudo apk add arch-install-scripts
mkdir ~/chroot && cd ~/chroot
curl -O https://mirrors.edge.kernel.org/archlinux/iso/latest/archlinux-bootstrap-2019.02.01-x86_64.tar.gz
sudo tar xzf archlinux-bootstrap-2019.02.01-x86_64.tar.gz && rm archlinux-bootstrap-2019.02.01-x86_64.tar.gz
sudo sed -i '/evowise/s/^#//' root.x86_64/etc/pacman.d/mirrorlist
sudo sed -i '/CheckSpace/s/^/#/' root.x86_64/etc/pacman.conf
sudo arch-chroot root.x86_64
[chroot]# pacman-key --init
[chroot]# pacman-key --populate archlinux

Once that is done, update the system and install the desired package(s) (denoted by ''"foo"'' in this example):

[chroot]# pacman -Syu ''foo''

=== Debian ===

Use the provided debootstrap package to create the Debian chroot. <code>--arch</code> is optional, depending of your needs.

On the '''linux-grsec''' kernel, you will need to relax chroot limitations:

sudo apk add debootstrap
for i in /proc/sys/kernel/grsecurity/chroot_*; do echo 0 | sudo tee $i; done
mkdir ~/chroot
sudo debootstrap --arch=i386 wheezy ~/chroot http://http.debian.net/debian/
for i in /proc/sys/kernel/grsecurity/chroot_*; do echo 1 | sudo tee $i; done
sudo chroot ~/chroot /bin/bash

You can now use <code>apt-get</code> to install needed packages.

[[Category:Development]]
[[Category:Installation]]

Steam

2021-02-11T19:46:43Z

PureTryOut: /* My controllers aren't detected */

Steam

2021-02-11T10:51:33Z

PureTryOut: /* My controllers aren't detected */

[http://store.steampowered.com/about/ Steam] is a popular game distribution platform by Valve.

{{Note|Steam for Linux only supports Ubuntu LTS. Thus, do not turn to Valve for support for issues with Steam on Alpine Linux.}}

== Installation ==

Steam requires glibc to run, and thus doesn't straight up run on Alpine Linux.
To work around this problem, we'll use [https://wiki.alpinelinux.org/wiki/Flatpak Flatpak].
Make sure you have the Flathub repository installed.

# apk add flatpak
$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
$ flatpak install com.valvesoftware.Steam

After installation Steam can be started using it's .desktop file or on the command line:

$ flatpak run com.valvesoftware.Steam

== Troubleshooting ==

=== My controllers aren't detected ===

By default Steam doesn't have permission to read your controllers.
This can be fixed by installing an udev rule from the official Steam package.

$ curl -O https://repo.steampowered.com/steam/pool/steam/s/steam/steam_1.0.0.68.tar.gz
$ tar xzf steam_1.0.0.68.tar.gz
# install -Dm644 steam-launcher/subprojects/steam-devices/60-steam-input.rules -t /etc/udev/rules.d
# install -Dm644 steam-launcher/subprojects/steam-devices/60-steam-vr.rules -t /etc/udev/rules.d

Make sure to replace "1.0.0.68" with the latest version of the Steam package.
The versions available are listed at https://repo.steampowered.com/steam/pool/steam/s/steam

Steam

2021-02-11T10:43:23Z

PureTryOut: Created page with "[http://store.steampowered.com/about/ Steam] is a popular game distribution platform by Valve. {{Note|Steam for Linux only supports Ubuntu LTS. Thus, do not turn to Valve for..."

[http://store.steampowered.com/about/ Steam] is a popular game distribution platform by Valve.

{{Note|Steam for Linux only supports Ubuntu LTS. Thus, do not turn to Valve for support for issues with Steam on Alpine Linux.}}

== Installation ==

Steam requires glibc to run, and thus doesn't straight up run on Alpine Linux.
To work around this problem, we'll use [https://wiki.alpinelinux.org/wiki/Flatpak Flatpak].
Make sure you have the Flathub repository installed.

# apk add flatpak
$ flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
$ flatpak install com.valvesoftware.Steam

After installation Steam can be started using it's .desktop file or on the command line:

$ flatpak run com.valvesoftware.Steam

== Troubleshooting ==

=== My controllers aren't detected ===

By default Steam doesn't have permission to read your controllers.
This can be fixed by installing an udev rule.
The one from [https://raw.githubusercontent.com/rpmfusion/steam/master/60-steam-input.rules rpmfusion's Steam package] seems to work well.

$ curl -O https://raw.githubusercontent.com/rpmfusion/steam/master/60-steam-input.rules
# install -Dm644 60-steam-input.rules -t /etc/udev/rules.d
# udevadm control --reload-rules && udevadm trigger # or reboot

PipeWire

2021-02-03T16:13:05Z

PureTryOut: /* Screen sharing on Wayland */

{{Draft|The instructions below have not been thoroughly tested and may break things.}}

[https://pipewire.org/ PipeWire] is a multimedia processing engine that aims to improve audio and video handling on Linux.

== Prerequisites ==

=== Audio Group ===

Add your normal user to the <code>audio</code> group. The user must log in for this to take effect.

<pre>
# addgroup audio <user>
</pre>

=== D-Bus ===

PipeWire requires a running [https://www.freedesktop.org/wiki/Software/dbus/ D-Bus] session. If you use a full desktop environment this will probably be started automatically, but with minimal window managers it must be done manually.

<pre>
# apk add dbus dbus-openrc dbus-x11
# rc-service dbus start
# rc-update add dbus default
</pre>

Then use <code>dbus-launch</code> whenever you start an X or Wayland session. For example:
<pre>
$ dbus-launch --exit-with-session sway
</pre>

== Installation and configuration ==

<pre>
# apk add pipewire
</pre>

Enable the <code>snd_seq</code> kernel module for ALSA support.

<pre>
# modprobe snd_seq
# echo snd_seq >> /etc/modules
</pre>

=== Pulseaudio ===

PipeWire can run a [https://www.freedesktop.org/wiki/Software/PulseAudio/ Pulseaudio] daemon which should allow all existing Pulseaudio applications to be used with the PipeWire backend.

<pre>
# apk add pipewire-pulse
</pre>

To enable the Pulseaudio daemon edit <code>/etc/pipewire/pipewire.conf</code> and uncomment the following line:

<pre>
"/usr/bin/pipewire-pulse" = { "#args" = "-a tcp:4713" }
</pre>

If your PipeWire version is less than or equal to 0.3.18 you instead need to uncomment:

<pre>
exec /usr/bin/pipewire-pulse
</pre>

=== Jack ===

If you will be using PipeWire for [https://jackaudio.org/ Jack] applications install the required package and make system wide links to the PipeWire replacement Jack libraries (I have not had success using <code>pw-jack</code>). You will not need to start a Jack server.

<pre>
# apk add pipewire-jack
# ln -sf /usr/lib/pipewire-0.3/jack/libjackserver.so.0 /usr/lib/libjackserver.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjacknet.so.0 /usr/lib/libjacknet.so.0
# ln -sf /usr/lib/pipewire-0.3/jack/libjack.so.0 /usr/lib/libjack.so.0
</pre>

{{Note|These symlinks might be overwritten during updates.}}

=== Video ===

Video should work out-of-the-box with v4l2 devices (e.g. a lot of webcams) and [https://gstreamer.freedesktop.org/ GStreamer] applications.

=== Screen sharing on Wayland ===

You will need the right [https://github.com/flatpak/xdg-desktop-portal xdg-desktop-portal] backend for your desktop environment. Screen sharing is known to work on GNOME with <code>xdg-desktop-portal-gtk</code> and on KDE Plasma with <code>xdg-desktop-portal-kde</code> and Firefox.

== Usage ==

Start the PipeWire media server. You'll probably get quite a few errors but just ignore them for now.

<pre>
$ pipewire
</pre>

In a different terminal window check the default output device. I don't yet know how this default can be changed for all applications, so you'd better hope it's right!

<pre>
$ pw-cat -p --list-targets
</pre>

Test sound is working using an audio file in a format supported by [http://www.mega-nerd.com/libsndfile/ libsndfile] (e.g. flac, opus, ogg, wav).

<pre>
$ pw-cat -p test.flac
</pre>

If you have a microphone test recording audio is working.

<pre>
$ pw-cat -r --list-targets
$ pw-cat -r recording.flac
(Speak for a while then stop it with Ctrl+c)
$ pw-cat -p recording.flac
</pre>

Test Pulseaudio clients using a media player (most use Pulseaudio) and if you use Jack test that too:

<pre>
# apk add jack-example-clients
$ jack_simple_client
</pre>

You should hear a sustained beep.

If you are happy everything is working, make pipewire start automatically when your X or Wayland session starts. For example, you could add the <code>pipewire</code> command to <code>~/.xinitrc</code> or your window manager's config file.

== See Also ==

* [https://gitlab.freedesktop.org/pipewire/pipewire PipeWire source repository]
* [https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home PipeWire Wiki]
* [https://wiki.archlinux.org/index.php/PipeWire PipeWire on the ArchWiki]
* [https://wiki.gentoo.org/wiki/Pipewire PipeWire on the Gentoo Wiki]

[[Category:Multimedia]]

Upgrading Qt

2020-11-24T19:21:01Z

PureTryOut:

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 5.12.x to 5.14.x) upgrade:

* py3-qt5
* qt5-qtwebkit # is not part of the regular Qt releases
* kio-extras
* kdeclarative
* kwayland
* kwayland-integration
* kwayland-server
* plasma-framework
* breeze
* plasma-integration
* qqc2-desktop-style
* kwin
* kaidan # compiles it's QML files

Virtual Reality

2020-10-19T10:19:53Z

PureTryOut:

The <code>testing</code> branch contains packages to make use of Virtual Reality on Alpine Linux so make sure that is enabled.

[https://wiki.alpinelinux.org/wiki/Enable_Community_Repository#Using_testing_repositories_of_my_release_version How to Enable the Testing Repository]

= Initial setup =

You will need an [https://en.wikipedia.org/wiki/OpenXR OpenXR] runtime to run any applications on VR.
{{Cmd|# apk add monado}}

Monado itself includes some required drivers, and it'll also pull in OpenHMD and libsurvive which provide drivers for the HMD and positional tracking respectively.

= Running =

{{Cmd| $ monado-service}}

Any application that requires VR should automatically pick up your HMD.

You can use [https://gitlab.freedesktop.org/xrdesktop/xrdesktop xrdesktop] to interact with your desktop windows in VR if you're running KDE Plasma. Support for GNOME is in the works but as of now requires patches on top of GNOME which aren't packaged on Alpine.

{{Cmd|# apk add kwin-effect-xrdesktop}}

Make sure to enable <code>xrdesktop</code> in the settings, <code>Workspace -> Workspace Behaviour -> Desktop Effects -> xrdesktop</code>.

Optionally you can install a Plasma applet to easily toggle VR mode.

{{Cmd|# apk add kdeplasma-applets-xrdesktop}}

VR

2020-09-16T10:29:27Z

PureTryOut: Redirected page to Virtual Reality

#REDIRECT [[Virtual Reality]]

Virtual Reality

2020-09-16T10:28:10Z

PureTryOut: Add a new Virtual Reality page

The <code>testing</code> branch contains packages to make use of Virtual Reality on Alpine Linux so make sure that is enabled.

[https://wiki.alpinelinux.org/wiki/Enable_Community_Repository#Using_testing_repositories_of_my_release_version How to Enable the Testing Repository]

= Initial setup =
Make sure you install a driver relevant for your tracking system and HMD.

== OpenHMD ==
A Free and Open Source API and drivers for immersive technology, such as head mounted displays with built in head tracking. [https://github.com/OpenHMD/OpenHMD/wiki/Support-List A list of supported hardware by OpenHMD].

{{Cmd|# apk add openhmd}}

== OpenXR runtime ==
You will need an [https://en.wikipedia.org/wiki/OpenXR OpenXR] runtime to run any applications on VR.
{{Cmd|# apk add monado}}

= Running =
Any application that requires VR should automatically pick up your HMD.

You can use [https://gitlab.freedesktop.org/xrdesktop/xrdesktop xrdesktop] to interact with your desktop windows in VR if you're running KDE Plasma. Support for GNOME is in the works but as of now requires patches on top of GNOME which aren't packaged on Alpine.

{{Cmd|# apk add kwin-effect-xrdesktop}}

Make sure to enable <code>xrdesktop</code> in the settings, <code>Workspace -> Workspace Behaviour -> Desktop Effects -> xrdesktop</code>.

Optionally you can install a Plasma applet to easily toggle VR mode.

{{Cmd|# apk add kdeplasma-applets-xrdesktop}}

Comparison with other distros

2020-08-20T11:55:21Z

PureTryOut: /* Reinstalling a particular package */

Even if Alpine is designed to run from RAM, it has some similarities in package management with both Gentoo and Debian. This page outlines those similarities and differences, to help Debian and Gentoo users to use Alpine.

The page was originally copied from: http://gentoo-wiki.com/TIP_Converting_from_or_to_Debian

= Package management =
Where Gentoo has portage and emerge; Debian has, among others, apt; Alpine uses apk-tools. This section compares how apk-tools is used, in comparison to apt-get/aptitude and emerge.

Note that Gentoo is source-based, just like ports in FreeBSD are, while Debian uses pre-compiled binaries. Alpine is compiled using Gentoo's portage, but Alpine itself uses its own apk-tools binary package which is more similar to FreeBSD's binary packages.

== Updating package database ==
Gentoo will update the build-from-source scripts and are the updating of the database is takes much more time that updating the database for Debian or Alpine.

'''Alpine'''
apk update

'''Gentoo'''
emerge --sync

'''Debian'''
aptitude update

== Showing available updates ==
Show which packages have an update available:

'''Alpine'''
apk version -v
or:
apk version -v -l '<'

'''Gentoo'''
emerge --deep --update --pretend world

'''Debian'''
aptitude upgrade --simulate

== Updating a particular package ==
'''Alpine'''
apk add -u package1 package2
'''Debian'''
aptitude install package1 package2
'''Gentoo'''
emerge --update package1 package2

== Installing packages ==
'''Alpine'''
apk add package1 package2

For source compile, see the [[Aports tree]] and the [[abuild]] tool.

'''Gentoo'''
emerge package1 package2
'''Debian'''
apt-get install package1 package2
Debian source compile:
apt-get build-dep package1
apt-get source package1
(optional: customize the build by modifying the debian/rules makefile)
(or set environmental variables like DEB_BUILD_OPTIONS)
(note that this will make your bug reports invalid to the maintainer)
dpkg-buildpackage -rfakeroot -uc -b
dpkg -i generatedpackagename
Simplified source compile:
apt-get build-dep package1
apt-get -b source package1
(the packages are automatically generated using the -b switch above)

'''Note:''' This process can be used to backport packages from testing and unstable by simply adding their respective source repositories to sources.list, which is similar to adding ~x86 to package.keywords in Gentoo. This is explored further in the "Architectures and repositories" section below.

== Reinstalling a particular package ==
'''Alpine'''
apk del package1 && apk add package1
or:
apk fix package1 package1
'''Gentoo'''
emerge --oneshot package1
'''Debian'''
apt-get install --reinstall package1 package1

Note: You ''rarely'' need to reinstall a package on Debian

== Searching the package database ==
'''Alpine'''

Alpine will only search package names.
apk search searchword

'''Gentoo'''

To search the package names and descriptions:
emerge --searchdesc searchword
'''Note:''' On Gentoo, it's actually much better to install and use either the esearch package or the eix package to do a search. You use them like this:
eix searchword

or

esearch searchword

'''Debian'''

apt-cache search searchword
Both emerge and apt-cache search support regular expressions.

To get the long package information on Debian (searching only in package names):
apt-cache search --full --names-only searchword

== Removing packages ==
'''Alpine'''

apk del package1 package2
apk del will remove configuration files when the --purge flag is used. Make sure you have backups of your configuration files. (Using rcs might be an idea)

You will mostly like to take a quick look at the dependencies before you remove packages recursively.

To see dependencies for a package, use:
apk info -R package1 package2

To see if package is required by other packages (is a dependency for another packages), use:
apk info -r package1 package2

'''Gentoo'''
emerge --unmerge package1 package2 (Note: this is unsafe as it does not check dependencies)
emerge --depclean package1 package2 (This will check dependencies)

'''Debian'''
apt-get remove package1 package2
or to remove along with all configuration files
apt-get remove --purge package1 package2

== Only downloading packages ==
This can be useful e.g. if you're on a dial-up connection and want to download everything first and install later.

'''Alpine'''
apk fetch package1 package2
'''Gentoo'''
emerge --fetchonly package1 package2
'''Debian'''
apt-get install --download-only package1 package2

== Cleaning up downloaded packages ==
Compressed packages that were downloaded for installation can easily consume gigabytes of storage space.

'''Alpine'''

Alpine will clean up packages automatically.

'''Gentoo'''
rm -rf /usr/portage/distfiles/*
To only remove outdated packages you will need to install the gentoolkit package and use eclean:
eclean distfiles
Cleaning temporary files from emerging packages:
rm -rf /var/tmp/portage/*

'''Debian'''
apt-get clean
Only remove outdated packages:
apt-get autoclean

==Reverse dependencies==

'''Alpine'''

apk-tools will take care of reverse dependencies.

'''Gentoo'''

Reverse dependencies are a major drawback of Gentoo's current portage implementation: It does not take care of them at all at the moment.
If you use the unsafe --unmerge argument, this means that you can uninstall packages needed by others without being warned about it. E.g. you can remove the X server package without portage warning you that KDE (which you have installed as well) depends on it. This way you can actually break your entire system (e.g. by removing glibc).

revdep-rebuild
can fix broken dependencies broken by
emerge --depclean

Recent versions of portage include library tracking and preservation with the preserved-libs feature. Portage will notify you to run {{Cmd| emerge @preserved-rebuild}} to help rebuild binaries that might otherwise become broken.

'''Debian'''

Reverse dependencies are taken care of by dpkg.

= Runlevel & Initscripts =
Runlevels work pretty conventionally on Debian (see details: [http://archive.fo/ZdZIz systemd]). On Alpine and Gentoo, they are a bit different.

== Directories and files ==
In '''Debian''', runlevels are named conventionally (0-6 and S). They are represented by directories in /etc/ called rc*.d (when the default sysv-rc boot loader package is installed; file-rc can be installed instead, and then the relevant file is runlevel.conf).

* /etc/rc0.d
* /etc/rc1.d
* /etc/rcS.d
* /etc/rc2.d
* /etc/rc3.d
* /etc/rc4.d
* /etc/rc5.d
* /etc/rc6.d

In '''Gentoo''', runlevels have the same names, but these are mapped to more self explanatory ones (in /etc/inittab): "boot", "default", "nonetwork", with the option to add more. The directories that represent them are in
/etc/runlevels/:
* /etc/runlevels/boot
* /etc/runlevels/default
* /etc/runlevels/nonetwork

In '''Gentoo''', if a service is not explicitly started in a runlevel, it is stopped when switching to that runlevel! There is no explicit stopping of runlevels as in Debian (/etc/rc?.d/K??service).

In '''both Debian and Gentoo''', which things are started (and stopped) in which runlevels is controlled by links in the runlevel directories to scripts in /etc/init.d/, e.g.:
'''Gentoo'''
$ ls -l /etc/runlevels/boot/hostname
lrwxrwxrwx 1 root root 20 Mar 25 2004 /etc/runlevels/boot/hostname -> /etc/init.d/hostname

'''Debian'''
$ ls -l rcS.d/S40hostname.sh
lrwxrwxrwx 1 root root 21 2004-11-07 00:19 rcS.d/S40hostname.sh -> ../init.d/hostname.sh

'''Alpine'''
In Alpine, runlevels work like they do in Gentoo:

* /etc/runlevels/boot
* /etc/runlevels/default
* /etc/runlevels/sysinit
* /etc/runlevels/nonetwork
* /etc/runlevels/shutdown

== Runlevel management ==
To manage which things to start in which runlevels, use the following commands:

'''Alpine'''

To see current status of services in runlevels, do:
rc-status
To add sshd to default runlevel, do:
rc-update add -k sshd default
The -k option will make sure sshd is stopped when shutting down or reboot.
To remove sshd from all runlevels do:
rc-update del sshd

'''Gentoo'''

rc-update
To add the cupsd to the default runlevel, do:
rc-update add cupsd default
To remove alsasound from the boot runlevel, do:
rc-update del alsasound boot
Also see this wiki page about [http://gentoo-wiki.com/Rc-update gentoo runlevel management with rc-update]

'''Debian'''

update-rc.d
Configure cupsd to be started in runlevels 2, 3, 4, 5, and stopped in 0, 1, 6, with sequence code 20:
update-rc.d cupsd start 20 2 3 4 5 . stop 20 0 1 6 .
or simply:
update-rc.d cupsd defaults
Remove cupsd from all runlevels:
update-rc.d -f cupsd remove

= Config Files =

== /etc/portage/make.conf and use flags ==
While in Gentoo there's a large number of configuration files which control the behaviour of the package management system, there are comparatively fewer in Debian, as there is no need to dictate how to compile software which is downloaded and tweak/alter it. In Gentoo, the file /etc/portage/make.conf is used for much configuration; this includes ''USE'' flags, which influence which elements of packages are compiled, and which libraries to build support for - common USE flags (USE or -USE to specifically negate support) include 'gtk gnome' for Gnome users (and a corresponding -qt -kde -arts) and 'qt kde arts' for KDE users. A Gentoo user's complete set of use flags may look something like this:

'''USE="-kde -arts -qt xv truetype bluetooth crypt slang readline gpm berkdb mmx gdbm tcpd pam libwww ssl nls ethereal perl python esd gif imlib sdl oggvorbis mpeg gnome gtk X motif opengl avi png tiff nptl pcmcia nptl ldap eds"'''

== Architectures and repositories ==
'''Gentoo'''

Also in /etc/portage/make.conf is the '''ACCEPT_KEYWORDS''' setting, with (for an X86-based processor) two settings, '''x86''' for stabler packages, and '''~x86''' for bleeding edge packages. It is however not recommended to make this change in /etc/portage/make.conf. Rather configure this per-package in /etc/portage/package.accept_keywords. It's enough to put a line into that file naming the package (for example 'app-foo/bar'). That file might look like this:

app-crypt/gpg-agent
app-text/docbook-xsl-stylesheets
=app-text/docbook-xml-dtd-4.3-r1

The last line says, that ''only'' version 4.3-r1 should be unmasked. Older and newer versions will still be ignored.

'''Note for non-x86 users:'''
The keywords '''x86''' and '''~x86''' can of course be replaced by '''sparc''' and '''~sparc''' for example.

'''Debian'''

Setting this in Debian is slightly more complicated, and is accomplished by setting different 'repositories' in ''/etc/apt/sources.list'' - along with which 'tree' to use for packages; in Debian, these are '''stable''', '''testing''', and '''unstable'''. An ''/etc/apt/sources.list'' file for a debian testing user may look something like this:

deb http://mirrors.kernel.org/debian testing main non-free contrib
deb ftp://ftp.nerim.net/debian-marillat testing main
deb http://security.debian.org testing/updates main contrib non-free

Alternatively, ''/etc/apt/sources.list'' can contain any number of repositories for any trees, and a default tree (this can be overridden using the -t switch on the command line) in ''/etc/apt/apt.conf'':

APT::Default-Release "testing";

Per-package settings go in ''/etc/apt/preferences'', somewhat like Gentoo's ''/etc/portage/package.keywords''.

== Network ==

'''Alpine'''

Alpine uses /etc/network/interfaces, just like Debian. The main reason is because this is the way busybox does it.

''/etc/network/interfaces'':
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255

auto eth0:0
iface eth0:0 inet static
address 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
# etc.

'''Gentoo'''

''/etc/conf.d/net'':
config_eth0="192.168.1.100 netmask 255.255.255.0
192.168.2.100 netmask 255.255.255.0"
routes_eth0="default via 192.168.1.1"

Note that this has changed recently. For more information please refer to http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4

'''Debian'''

''/etc/network/interfaces'':
auto eth0
iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0
broadcast 192.168.0.255

auto eth0:0
iface eth0:0 inet static
address 192.168.1.1
netmask 255.255.255.0
broadcast 192.168.1.255
# etc.

= Comparison chart/Rosetta Stone =

This chart shows how some standard things are done in Alpine compared to other distributions.

{| cellpadding="5" border="1" class="wikitable"
|-
! Action
! Alpine ([http://wiki.alpinelinux.org/wiki/Alpine_Linux_package_management apk])
! Arch Linux ([https://wiki.archlinux.org/index.php/Pacman pacman])
! Gentoo ([http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 emerge])
! Debian/Ubuntu ([http://wiki.debian.org/Aptitude aptitute])
! Fedora/RHEL/SL/Centos ([http://yum.baseurl.org/wiki/YumCommands yum])
|-
| Update package database
| {{Cmd| apk update}}
| {{Cmd| pacman -Sy}}
| {{Cmd| emerge --sync}}
| {{Cmd| aptitude update}}
| {{Cmd| yum update}}
|-
| Showing available updates
| {{Cmd| apk version -l '<'}}
| {{Cmd| pacman -Qu}}
| {{Cmd| emerge --deep --update --pretend @world}}
| {{Cmd| aptitude upgrade --simulate}}
| {{Cmd| yum list updates}}
|-
| Installing packages
| {{Cmd| apk add [package name]}}
| {{Cmd| pacman -S [package name]}}
| {{Cmd| emerge [package name]}}
| {{Cmd| aptitude install [package name]}}
| {{Cmd| yum install [package name]}}
|-
| Update all installed packages
| {{Cmd| apk upgrade -U -a}}
| {{Cmd| pacman -Su}}
| {{Cmd| emerge --update --deep @world}}
| {{Cmd| aptitude upgrade}}
| {{Cmd| yum update}}
|-
| Searching package database
| {{Cmd| apk search -v '[string]*'}}
| {{Cmd| pacman -Ss [string]}}
| {{Cmd| emerge --search [string]}}
| {{Cmd| aptitude search [string]}}
| {{Cmd| yum search [string]}}
|-
| Removing packages
| {{Cmd| apk del [package name]}}
| {{Cmd| pacman -R [package name]}}
| {{Cmd| emerge --depclean [package name]}}
| {{Cmd| aptitude remove [package name]}}
| {{Cmd| yum remove [package name]}}
|}

[[Category:Package Manager]]

Upgrading Qt

2020-07-14T20:16:42Z

PureTryOut:

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 5.12.x to 5.14.x) upgrade:

* py3-qt5
* qt5-qtwebkit # is not part of the regular Qt releases
* kio-extras
* kdeclarative
* kwayland
* kwayland-integration
* plasma-framework
* breeze
* plasma-integration
* qqc2-desktop-style
* kwin
* kaidan # compiles it's QML files
* ruqola # compiles it's QML files

KDE

2020-05-30T09:18:29Z

PureTryOut: /* From the console */

{{TOC right}}

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

Note that the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. The rest of Plasma can however be installed separately to get a functional desktop.

= Installation =

=== Plasma ===

Before installation, make sure your graphical environment is setup. Don't be fooled by the name of the command, this is also required for Wayland sessions.
{{Cmd|setup-xorg-base}}

Install the {{Pkg|plasma}} meta-package. This will install the required Plasma packages and {{Pkg|sddm}} and pre-configure it to use the Breeze theme. Alternatively a more minimal installation can be done by installing {{Pkg|plasma-desktop}}.

=== KDE Applications ===

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a more limited set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

= Starting Plasma =

Plasma can be started using a display manager or from the console.

=== Using a display manager ===

When Plasma is installed via the {{Pkg|plasma}} meta-package, this has already been setup using {{Pkg|sddm}}.

* Select ''Plasma'' to launch a new session in Xorg
* Select ''Plasma (Wayland)'' to launch a new session in Wayland

=== From the console ===

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startplasma-x11</code> to your <code>.xinitrc</code> file. Then just start X.
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
</pre>

=See also=
* [[Flatpak]]

[[category:Desktop]]

Upgrading Qt

2020-04-10T23:12:22Z

PureTryOut:

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 5.12.x to 5.14.x) upgrade:

* py3-qt5
* kio-extras
* kdeclarative
* kwayland
* kwayland-integration
* plasma-framework
* breeze
* plasma-integration
* qqc2-desktop-style
* kwin
* kaidan - compiles it's QML files
* ruqola - compiles it's QML files

Bluetooth audio

2020-03-28T16:41:51Z

PureTryOut: Removed obsolete section about editing Bluetooth config

== PulseAudio ==

Before you can connect your device to Bluetooth speakers or headphones, you'll have to make sure {{Pkg|pulseaudio-bluez}} is installed.

Upgrading Qt

2020-03-27T14:04:58Z

PureTryOut:

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 5.12.x to 5.14.x) upgrade:

* py3-qt5
* kio-extras
* kdeclarative
* kwayland
* kwayland-integration
* plasma-framework
* breeze
* plasma-integration
* qqc2-desktop-style
* kwin
* kaidan - compiles it's QML files

Upgrading Qt

2020-02-25T09:08:05Z

PureTryOut: Created page with "When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every..."

When Qt gets upgraded between major versions, we have to rebuild some packages due to ABI changes and private API usages. The following is a list of packages to bump on every major (e.g. 5.12.x to 5.14.x) upgrade:

* py3-qt5
* kio-extras
* kdeclarative
* kwayland
* kwayland-integration
* plasma-framework
* breeze
* plasma-integration
* qqc2-desktop-style
* kwin

Setting up disks manually

2020-02-09T19:30:36Z

PureTryOut: /* Custom partitioning */

{{Draft|Some information on this page may be incomplete or outdate.}}

You may have complex needs that aren't handled automatically by the [[Alpine Setup Scripts]]. In those cases, you'll need to prepare your disks manually.

It is possible to have one or more of RAID, encryption, and/or LVM on your {{Path|/}} (root) volume. However, the Alpine init script only knows how to handle them when they're layered in that order, and your initram and extlinux.conf file in the {{Path|/boot}} partition are configured properly.

Your {{Path|/boot}} cannot reside on an encrypted or LVM volume, at least not with Alpine's default bootloader (extlinux). (Grub2 can deal with {{Path|/boot}} being on an LVM volume.) The usual practice is to create a small partition for {{Path|/boot}}, and then devote the rest of your disk to a separate partition on which you layer one or more of RAID, encryption, and/or LVM.

Sometimes {{Path|/boot}} is also setup as a mirrored (RAID1) volume, however this is just for post-init access. That way, when you write a new kernel or bootloader config file to {{Path|/boot}}, it gets written to multiple physical partitions. During the pre-init, bootloader phase, only one of those partitions will be read from.

So, typical setups might look like this:

<pre>
One-disk system
---------------
+------------------------------------------------+
| small partition (32--100M), holding |
| only /boot, filesystem needn't be journaled |
+------------------------------------------------+
| rest of disk in second partition |
| +------------------------------------------+ |
| | cryptsetup volume | |
| | +-------------------------------------+ | |
| | | LVM PV, containing single VG, | | |
| | | containing multiple LVs, holding | | |
| | | /, /home, swap, etc | | |
| | +-------------------------------------+ | |
| +------------------------------------------+ |
+------------------------------------------------+

Two-disk system
---------------
+------------------------------------------------+ +------------------------------------------------+
| small partition (32--100M), holding | | small partition (32--100M), holding | These 2 partitions might
| only /boot, filesystem needn't be journaled | | only /boot, filesystem needn't be journaled | form a mirrored (RAID1)
+------------------------------------------------+ +------------------------------------------------+ volume
| rest of disk in second partition | | rest of disk in second partition |
| T================================================================================================T | These 2 partitions form
| T +--------------------------------------------------------------------------------------------+ T | a second mirrored
| T | cryptsetup volume | T | (RAID1) volume
| T | +---------------------------------------------------------------------------------------+ | T |
| T | | LVM PV, containing single VG, | | T |
| T | | containing multiple LVs, holding | | T |
| T | | /, /home, swap, etc | | T |
| T | +---------------------------------------------------------------------------------------+ | T |
| T +--------------------------------------------------------------------------------------------+ T |
| T================================================================================================T |
| | | |
+------------------------------------------------+ +------------------------------------------------+

</pre>

In a three-disk system, the {{Path|/boot}} would still be RAID1, but the larger partition might in that case be RAID5.

=== RAID ===
<code>setup-disk</code> will automatically build a RAID array if you supply the '''-r''' switch, or if you specify more than one device.

If you instead want to build your RAID array manually, see [[Setting up a software RAID array]]. Then you can add additional layers of encryption and/or LVM, or just assemble the RAID array, and supply the {{Path|/dev/mdi}} device directly to [[setup-disk]]. When you're finished, be sure to disassemble the RAID array before rebooting.

If <code>setup-disk</code> sees that you're using RAID---either because you gave it the <code>-r</code> switch, or multiple devices, or a {{Path|/dev/mdi}} device---then it will setup your initramfs and extlinux.conf file properly. However, in other cases, such as when you're also using encryption, or you invoke <code>setup-disk</code> with a mounted directory argument, these might not be properly setup for RAID. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into:

{{Cmd|1=echo "/sbin/mdadm" > $MNT/etc/mkinitfs/files.d/raid
echo "/etc/mdadm.conf" >> $MNT/etc/mkinitfs/files.d/raid
# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..."
# includes raid (this field is space-separated and quoted)
mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT
# edit $MNT/etc/update-extlinux.conf to make sure modules=... contains
# raid1 or raid456 (whichever your / is on; this field is comma-separated)
# also check the root= setting
extlinux --raid --install $MNT/boot --update
}}

{{Todo|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

You might also need to manually tweak {{Path|$MNT/etc/fstab}}. And you might need to copy {{Path|/usr/share/syslinux/mbr.bin}} to your disk's MBR.

=== Encryption ===

See [[Setting up encrypted volumes with LUKS]]. Then you can add an additional layer of LVM, or just unlock the volume you've created (using <code>cryptsetup luksOpen ...</code>), and supply the {{Path|/dev/mapper/something}} device directly to [[setup-disk]]. When you're finished, be sure to relock the volume (using <code>cryptsetup luksClose ...</code>) before rebooting.

If you install your {{Path|/}} (root) on an encrypted volume, you'll need to manually edit/rebuild your initram and your extlinux.conf file. The following assumes that <code>$MNT</code> holds the root directory you're installing into, that you've created the cryptvolume on the device {{Path|/dev/md2}}, and that you want to unlock the encrypted volume into a virtual volume named "crypt":

{{Cmd|1=# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..."
# includes cryptsetup (this field is space-separated and quoted)
mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT
# edit $MNT/etc/update-extlinux.conf to make sure default_kernel_opts="..."
# contains cryptroot=/dev/md1 and cryptdm=crypt (this field is also space-separated and quoted)
# also check the root= setting
extlinux --install $MNT/boot --update
}}

{{Todo|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

You might also need to manually tweak {{Path|$MNT/etc/fstab}}.

=== LVM ===
<code>setup-disk</code> will automatically build and use volumes in a LVM group if you supply the '''-L''' switch.

If you instead want to build your LVM system manually, see [[Setting up Logical Volumes with LVM]]. Then <code>vgchange -ay</code>, format and mount your volumes, and supply the root mountpoint to [[setup-disk]]. When you're finished, be sure to
{{Cmd|umount ...
vgchange -an}}
before rebooting.

If <code>setup-disk</code> sees that you're using LVM---perhaps because you gave it the <code>-L</code> switch---then it will setup your initram and extlinux.conf file properly. However, in other cases, these might not be properly setup. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into:

{{Cmd|1=# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..."
# includes lvm (this field is space-separated and quoted)
mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT
# edit $MNT/etc/update-extlinux.conf to make sure root= is set correctly
extlinux --install $MNT/boot --update
}}

{{Todo|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

You might also need to manually tweak {{Path|$MNT/etc/fstab}}.

=== Custom partitioning ===
<code>setup-disk</code> will by default set up a root partition, a separate /boot partition and a swap. If you want a different layout you can manually create the partitions, filesystems and mount them up on {{Path|/mnt}} (or any other mount point) and then run:

{{Cmd|setup-disk /mnt}}

<code>setup-disk</code> will install your running system on the mounted root, detect your file system layout and generate a fstab.

If you're going for MBR, you are responsible for making the proper partition bootable and make sure the MBR is OK for extlinux. If you're going for EFI, make sure you set <code>BOOTLOADER=grub</code> and <code>USE_EFI=1</code> and {{Pkg|grub-efi}} and {{Pkg|efibootmgr}} are installed before running <code>setup-disk</code>.

See also [https://github.com/itoffshore/alpine-linux-scripts setup-partitions]

=== Dual-booting ===
See [[Installing Alpine on HDD dualbooting|Install to HDD with dual-boot]]

=== Other needs ===
* [[Installing Alpine Linux in a chroot]]
* [[Replacing non-Alpine Linux with Alpine remotely]]





== Setting up swap ==

# create partition with type "linux swap" (82) (If you're going to use an LVM logical volume for swap, skip this step and <code>lvcreate</code> that instead.)
# <code>mkswap /dev/sda2</code>
# <code>echo -e "/dev/sda2 none swap sw 0 0" >> /mnt/etc/fstab</code>
# <code>swapon /dev/sda2</code> (or <code>rc-service swap start</code>)

Then {{Cmd|free -m}} will show how much swap space is available (in MB).

If you prefer maximum speed, you don't need configure any raid devices for swap. Just add 2 swap partitions on different disks and linux will stripe them automatically. The downside is that at the moment one disk fails, the system will go down. For better reliability, put swap on RAID1.

{{Todo|Instructions for cryptswap?}}

= =
* [https://beta.docs.alpinelinux.org/user-handbook/0.1a/Installing/manual.html#_finalizing beta.docs.alpinelinux.org] ''([http://archive.md/2KQPQ archive])''

[[Category:Installation]]
[[Category:Storage]]

Setting up disks manually

2020-02-09T19:11:50Z

PureTryOut: /* Custom partitioning */

{{Draft|Some information on this page may be incomplete or outdate.}}

You may have complex needs that aren't handled automatically by the [[Alpine Setup Scripts]]. In those cases, you'll need to prepare your disks manually.

It is possible to have one or more of RAID, encryption, and/or LVM on your {{Path|/}} (root) volume. However, the Alpine init script only knows how to handle them when they're layered in that order, and your initram and extlinux.conf file in the {{Path|/boot}} partition are configured properly.

Your {{Path|/boot}} cannot reside on an encrypted or LVM volume, at least not with Alpine's default bootloader (extlinux). (Grub2 can deal with {{Path|/boot}} being on an LVM volume.) The usual practice is to create a small partition for {{Path|/boot}}, and then devote the rest of your disk to a separate partition on which you layer one or more of RAID, encryption, and/or LVM.

Sometimes {{Path|/boot}} is also setup as a mirrored (RAID1) volume, however this is just for post-init access. That way, when you write a new kernel or bootloader config file to {{Path|/boot}}, it gets written to multiple physical partitions. During the pre-init, bootloader phase, only one of those partitions will be read from.

So, typical setups might look like this:

<pre>
One-disk system
---------------
+------------------------------------------------+
| small partition (32--100M), holding |
| only /boot, filesystem needn't be journaled |
+------------------------------------------------+
| rest of disk in second partition |
| +------------------------------------------+ |
| | cryptsetup volume | |
| | +-------------------------------------+ | |
| | | LVM PV, containing single VG, | | |
| | | containing multiple LVs, holding | | |
| | | /, /home, swap, etc | | |
| | +-------------------------------------+ | |
| +------------------------------------------+ |
+------------------------------------------------+

Two-disk system
---------------
+------------------------------------------------+ +------------------------------------------------+
| small partition (32--100M), holding | | small partition (32--100M), holding | These 2 partitions might
| only /boot, filesystem needn't be journaled | | only /boot, filesystem needn't be journaled | form a mirrored (RAID1)
+------------------------------------------------+ +------------------------------------------------+ volume
| rest of disk in second partition | | rest of disk in second partition |
| T================================================================================================T | These 2 partitions form
| T +--------------------------------------------------------------------------------------------+ T | a second mirrored
| T | cryptsetup volume | T | (RAID1) volume
| T | +---------------------------------------------------------------------------------------+ | T |
| T | | LVM PV, containing single VG, | | T |
| T | | containing multiple LVs, holding | | T |
| T | | /, /home, swap, etc | | T |
| T | +---------------------------------------------------------------------------------------+ | T |
| T +--------------------------------------------------------------------------------------------+ T |
| T================================================================================================T |
| | | |
+------------------------------------------------+ +------------------------------------------------+

</pre>

In a three-disk system, the {{Path|/boot}} would still be RAID1, but the larger partition might in that case be RAID5.

=== RAID ===
<code>setup-disk</code> will automatically build a RAID array if you supply the '''-r''' switch, or if you specify more than one device.

If you instead want to build your RAID array manually, see [[Setting up a software RAID array]]. Then you can add additional layers of encryption and/or LVM, or just assemble the RAID array, and supply the {{Path|/dev/mdi}} device directly to [[setup-disk]]. When you're finished, be sure to disassemble the RAID array before rebooting.

If <code>setup-disk</code> sees that you're using RAID---either because you gave it the <code>-r</code> switch, or multiple devices, or a {{Path|/dev/mdi}} device---then it will setup your initramfs and extlinux.conf file properly. However, in other cases, such as when you're also using encryption, or you invoke <code>setup-disk</code> with a mounted directory argument, these might not be properly setup for RAID. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into:

{{Cmd|1=echo "/sbin/mdadm" > $MNT/etc/mkinitfs/files.d/raid
echo "/etc/mdadm.conf" >> $MNT/etc/mkinitfs/files.d/raid
# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..."
# includes raid (this field is space-separated and quoted)
mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT
# edit $MNT/etc/update-extlinux.conf to make sure modules=... contains
# raid1 or raid456 (whichever your / is on; this field is comma-separated)
# also check the root= setting
extlinux --raid --install $MNT/boot --update
}}

{{Todo|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

You might also need to manually tweak {{Path|$MNT/etc/fstab}}. And you might need to copy {{Path|/usr/share/syslinux/mbr.bin}} to your disk's MBR.

=== Encryption ===

See [[Setting up encrypted volumes with LUKS]]. Then you can add an additional layer of LVM, or just unlock the volume you've created (using <code>cryptsetup luksOpen ...</code>), and supply the {{Path|/dev/mapper/something}} device directly to [[setup-disk]]. When you're finished, be sure to relock the volume (using <code>cryptsetup luksClose ...</code>) before rebooting.

If you install your {{Path|/}} (root) on an encrypted volume, you'll need to manually edit/rebuild your initram and your extlinux.conf file. The following assumes that <code>$MNT</code> holds the root directory you're installing into, that you've created the cryptvolume on the device {{Path|/dev/md2}}, and that you want to unlock the encrypted volume into a virtual volume named "crypt":

{{Cmd|1=# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..."
# includes cryptsetup (this field is space-separated and quoted)
mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT
# edit $MNT/etc/update-extlinux.conf to make sure default_kernel_opts="..."
# contains cryptroot=/dev/md1 and cryptdm=crypt (this field is also space-separated and quoted)
# also check the root= setting
extlinux --install $MNT/boot --update
}}

{{Todo|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

You might also need to manually tweak {{Path|$MNT/etc/fstab}}.

=== LVM ===
<code>setup-disk</code> will automatically build and use volumes in a LVM group if you supply the '''-L''' switch.

If you instead want to build your LVM system manually, see [[Setting up Logical Volumes with LVM]]. Then <code>vgchange -ay</code>, format and mount your volumes, and supply the root mountpoint to [[setup-disk]]. When you're finished, be sure to
{{Cmd|umount ...
vgchange -an}}
before rebooting.

If <code>setup-disk</code> sees that you're using LVM---perhaps because you gave it the <code>-L</code> switch---then it will setup your initram and extlinux.conf file properly. However, in other cases, these might not be properly setup. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into:

{{Cmd|1=# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..."
# includes lvm (this field is space-separated and quoted)
mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT
# edit $MNT/etc/update-extlinux.conf to make sure root= is set correctly
extlinux --install $MNT/boot --update
}}

{{Todo|Does adding the <code>--update</code> option to <code>extlinux ...</code> suffice to make {{Path|/boot/extlinux.conf}} be regenerated? Or do we need to manually tweak that file, or run <code>update-extlinux</code>, as well?}}

You might also need to manually tweak {{Path|$MNT/etc/fstab}}.

=== Custom partitioning ===
<code>setup-disk</code> will by default set up a root partition, a separate /boot partition and a swap. If you want a different layout you can manually create the partitions, filesystems and mount them up on {{Path|/mnt}} (or any other mount point) and then run:

{{Cmd|setup-disk /mnt}}

<code>setup-disk</code> will install your running system on the mounted root, detect your file system layout and generate a fstab.

If you're going for MBR, you are responsible for making the proper partition bootable and make sure the MBR is OK for extlinux. If you're going for EFI, make sure you set <code>BOOTLOADER=grub</code> and <code>USE_EFI=1</code> and {{Pkg|grub-efi}} is installed before running <code>setup-disk</code>.

See also [https://github.com/itoffshore/alpine-linux-scripts setup-partitions]

=== Dual-booting ===
See [[Installing Alpine on HDD dualbooting|Install to HDD with dual-boot]]

=== Other needs ===
* [[Installing Alpine Linux in a chroot]]
* [[Replacing non-Alpine Linux with Alpine remotely]]





== Setting up swap ==

# create partition with type "linux swap" (82) (If you're going to use an LVM logical volume for swap, skip this step and <code>lvcreate</code> that instead.)
# <code>mkswap /dev/sda2</code>
# <code>echo -e "/dev/sda2 none swap sw 0 0" >> /mnt/etc/fstab</code>
# <code>swapon /dev/sda2</code> (or <code>rc-service swap start</code>)

Then {{Cmd|free -m}} will show how much swap space is available (in MB).

If you prefer maximum speed, you don't need configure any raid devices for swap. Just add 2 swap partitions on different disks and linux will stripe them automatically. The downside is that at the moment one disk fails, the system will go down. For better reliability, put swap on RAID1.

{{Todo|Instructions for cryptswap?}}

= =
* [https://beta.docs.alpinelinux.org/user-handbook/0.1a/Installing/manual.html#_finalizing beta.docs.alpinelinux.org] ''([http://archive.md/2KQPQ archive])''

[[Category:Installation]]
[[Category:Storage]]

Bluetooth audio

2019-12-31T15:40:11Z

PureTryOut: /* PulseAudio */

== PulseAudio ==

Before you can connect your device to Bluetooth speakers or headphones, you'll have to make sure {{Pkg|pulseaudio-bluez}} is installed.

Edit <code>/etc/bluetooth/main.conf</code> and add <code>Enable=Source,Sink,Media,Socket</code> under the <code>[General]</code> section, then restart the Bluetooth service <code># rc-service bluetooth restart</code>.
Once you connect to the Bluetooth device, a new output will appear in the audio settings.

Bluetooth audio

2019-12-31T15:39:55Z

PureTryOut:

== PulseAudio ==

Before you can connect your device to Bluetooth speakers or headphones, you'll have to make sure {{Pkg|pulseaudio-bluez}} is installed.

Edit <code>/etc/bluetooth/main.conf</code> and add <code>Enable=Source,Sink,Media,Socket</code> under the <code>[General]</code> section, then restart the Bluetooth service `<code># rc-service bluetooth restart</code>.
Once you connect to the Bluetooth device, a new output will appear in the audio settings.

Bluetooth audio

2019-12-31T15:39:09Z

PureTryOut: Created page with "== PulseAudio == Before you can connect your device to Bluetooth speakers or headphones, you'll have to make sure {{Pkg|pulseaudio-bluez}} is installed. Edit <code>/etc/blue..."

== PulseAudio ==

Before you can connect your device to Bluetooth speakers or headphones, you'll have to make sure {{Pkg|pulseaudio-bluez}} is installed.

Edit <code>/etc/bluetooth/main.conf</code> and add <code>Enable=Source,Sink,Media,Socket</code> under the <code>[General]</code> section.
Once you connect to the Bluetooth device, a new output will appear in the audio settings.

Pine64 A64 LTS

2019-12-19T14:15:48Z

PureTryOut:

{{Draft|It doesn't boot yet}}

Since the 3.10.0 release, Alpine Linux includes [https://denx.de/ u-boot] support for the [https://pine64.org/ Pine64] A64LTS. Since the 3.11.0 release, Alpine Linux includes a kernel that is new enough to boot it. This page describes how to install the system.

The generic (u-boot) ARM image should be used. Make sure your sdcard is empty before you install Alpine Linux, as all it's contents will be removed!

# download the [http://dl-cdn.alpinelinux.org/alpine/v3.11/releases/aarch64/ generic ARM image] and unpack it somewhere
# write u-boot to the sdcard <code>cd <unpacked folder>/u-boot/pine64-lts && dd if=u-boot-sunxi-with-spl.bin of=/path/to/sdcard bs=1024 seek=8</code>
# create a new partition on the sdcard starting from sector 2048, set it as bootable
# format it to ext4 (or any other filesystem that u-boot supports booting from)
# decompress (<code>gunzip</code>)the kernel image (<code>boot/vmlinuz-lts</code>) as the device's u-boot can't boot from a compressed kernel
# copy over the <code>apks</code>, <code>boot</code> and <code>extlinux</code> folders from the extracted archive to the new partition

Alpine Linux should now boot on your device.

[[category:ARM]]

Pine64 A64 LTS

2019-12-18T13:21:52Z

PureTryOut:

{{Draft|It doesn't boot yet}}

Since the 3.10.0 release, Alpine Linux includes [https://denx.de/ u-boot] support for the [https://pine64.org/ Pine64] A64LTS. Since the 3.11.0 release, Alpine Linux includes a kernel that is new enough to boot it. This page describes how to install the system.

The generic (u-boot) ARM image should be used. Make sure your sdcard is empty before you install Alpine Linux, as all it's contents will be removed!

# download the [http://dl-cdn.alpinelinux.org/alpine/v3.11/releases/aarch64/ generic ARM image] and unpack it somewhere
# write u-boot to the sdcard <code>cd <unpacked folder>/u-boot/pine64-lts && dd if=u-boot-sunxi-with-spl.bin of=/path/to/sdcard bs=1024 seek=8</code>
# create a new partition on the sdcard starting from sector 2048, set it as bootable
# format it to ext4 (or any other filesystem that u-boot supports booting from)
# copy over the <code>apks</code>, <code>boot</code> and <code>extlinux</code> folders from the extracted archive to the new partition

Alpine Linux should now boot on your device.

[[category:ARM]]

KDE

2019-12-14T15:36:19Z

PureTryOut: /* From the console */

{{TOC right}}

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

Note that the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. The rest of Plasma can however be installed separately to get a functional desktop.

= Installation =

=== Plasma ===

Before installation, make sure your graphical environment is setup. Don't be fooled by the name of the command, this is also required for Wayland sessions.
{{Cmd|setup-xorg-base}}

Install the {{Pkg|plasma}} meta-package. This will install the required Plasma packages and {{Pkg|sddm}} and pre-configure it to use the Breeze theme. Alternatively a more minimal installation can be done by installing {{Pkg|plasma-desktop}}.

=== KDE Applications ===

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a more limited set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

= Starting Plasma =

Plasma can be started using a display manager or from the console.

=== Using a display manager ===

When Plasma is installed via the {{Pkg|plasma}} meta-package, this has already been setup using {{Pkg|sddm}}.

* Select ''Plasma'' to launch a new session in Xorg
* Select ''Plasma (Wayland)'' to launch a new session in Wayland

=== From the console ===

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startkde</code> to your <code>.xinitrc</code> file. Then just start X.
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland
</pre>

=See also=
* [[Flatpak]]

[[category:Desktop]]

KDE

2019-10-20T16:44:52Z

PureTryOut: /* Installation */

{{TOC right}}

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

Note that the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. The rest of Plasma can however be installed separately to get a functional desktop.

= Installation =

=== Plasma ===

Before installation, make sure your graphical environment is setup. Don't be fooled by the name of the command, this is also required for Wayland sessions.
{{Cmd|setup-xorg-base}}

Install the {{Pkg|plasma}} meta-package. This will install the required Plasma packages and {{Pkg|sddm}} and pre-configure it to use the Breeze theme. Alternatively a more minimal installation can be done by installing {{Pkg|plasma-desktop}}.

=== KDE Applications ===

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a more limited set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

= Starting Plasma =

Plasma can be started using a display manager or from the console.

=== Using a display manager ===

When Plasma is installed via the {{Pkg|plasma}} meta-package, this has already been setup using {{Pkg|sddm}}.

* Select ''Plasma'' to launch a new session in Xorg
* Select ''Plasma (Wayland)'' to launch a new session in Wayland

=== From the console ===

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startkde</code> to your <code>.xinitrc</code> file. Then just start X.
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasmacompositor
</pre>

[[category:Desktop]]

KDE

2019-10-20T16:42:50Z

PureTryOut:

{{TOC right}}

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

Note that the {{Pkg|plasma}} package isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|kdeplasma-addons}} dependency not being available there. The rest of Plasma can however be installed separately to get a functional desktop.

= Installation =

=== Plasma ===

Before installation, make sure Xorg is setup.
{{Cmd|setup-xorg-base}}

Install the {{Pkg|plasma}} meta-package. This will install the required Plasma packages and {{Pkg|sddm}} and pre-configure it to use the Breeze theme. Alternatively a more minimal installation can be done by installing {{Pkg|plasma-desktop}}.

=== KDE Applications ===

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a more limited set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

= Starting Plasma =

Plasma can be started using a display manager or from the console.

=== Using a display manager ===

When Plasma is installed via the {{Pkg|plasma}} meta-package, this has already been setup using {{Pkg|sddm}}.

* Select ''Plasma'' to launch a new session in Xorg
* Select ''Plasma (Wayland)'' to launch a new session in Wayland

=== From the console ===

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startkde</code> to your <code>.xinitrc</code> file. Then just start X.
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasmacompositor
</pre>

[[category:Desktop]]

Pine64 A64 LTS

2019-08-23T12:45:00Z

PureTryOut:

{{Draft|It doesn't boot yet}}

Since the 3.10.0 release, Alpine Linux includes u-boot support for the Pine64 A64LTS. The <code>linux-vanilla</code> kernel is still too old to boot it, however this page describes how to install the system for once the kernel is upgraded.

The generic ARM image should be used. Make sure your sdcard is empty before you install Alpine Linux, as all it's contents will be removed!

# download the generic ARM image and unpack it somewhere
# write u-boot to the sdcard <code><unpacked folder>/u-boot/pine64-lts/dd if=u-boot-sunxi-with-spl.bin of=/path/to/sdcard bs=1024 seek=8</code>
# create a new partition on the sdcard starting from sector 2048, set it as bootable
# format it to ext4 (or any other filesystem that u-boot supports booting from)
# copy over the <code>apk</code>, <code>boot</code> and <code>extlinux</code> folders from the extracted archive to the new partition

Alpine Linux should now boot on your device.

KDE

2019-07-13T21:57:36Z

PureTryOut:

KDE is a software project comprising a desktop environment known as Plasma, a collection of libraries and frameworks known as KDE Frameworks, and several applications known as KDE Applications. Their [https://userbase.kde.org/Welcome_to_KDE_UserBase UserBase wiki] has detailed information about most KDE Applications.

Note that Plasma isn't available for the <code>ppc64le</code> and <code>s390x</code> architectures due to the {{Pkg|qt5-qtwebengine}} dependency not being available there. KDE Frameworks however is and so are several KDE Applications.

= Installation =

=== Plasma ===

Before installation, make sure Xorg is setup.
{{Cmd|setup-xorg-base}}

Install the {{Pkg|plasma}} meta-package. This will install the required Plasma packages and {{Pkg|sddm}} and pre-configure it to use the Breeze theme. Alternatively a more minimal installation can be done by installing {{Pkg|plasma-desktop}}.

=== KDE Applications ===

To install the full set of KDE Applications, install {{Pkg|kde-applications}}. You can also choose to install a more limited set of applications by installing any of the subpackages:

* {{Pkg|kde-applications-accessibility}}
* {{Pkg|kde-applications-admin}}
* {{Pkg|kde-applications-base}}
* {{Pkg|kde-applications-edu}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-games}}
* {{Pkg|kde-applications-graphics}}
* {{Pkg|kde-applications-multimedia}}
* {{Pkg|kde-applications-network}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-pim}}, not available for <code>ppc64le</code> and <code>s390x</code>
* {{Pkg|kde-applications-sdk}}
* {{Pkg|kde-applications-utils}}
* {{Pkg|kde-applications-webdev}}

= Starting Plasma =

Plasma can be started using a display manager or from the console.

=== Using a display manager ===

When Plasma is installed via the {{Pkg|plasma}} meta-package, this has already been setup using {{Pkg|sddm}}.

* Select ''Plasma'' to launch a new session in Xorg
* Select ''Plasma (Wayland)'' to launch a new session in Wayland

=== From the console ===

The Xorg session can be launched by installing {{Pkg|xinit}} and appending <code>exec startkde</code> to your <code>.xinitrc</code> file. Then just start X.
{{Cmd|xinit}}

For the Wayland session run
<pre>
XDG_SESSION_TYPE=wayland dbus-run-session startplasmacompositor
</pre>

Create UEFI boot USB

2019-07-04T14:49:43Z

PureTryOut:

{{Note | These manual steps aren't required anymore, as the latest release images can just be written to an USB like normal and will support UEFI booting}}

This article explains how to create an UEFI boot USB with parted and gummiboot.

In this example we will use {{Path|/dev/sdX}}. This will be different depending on your system.

== Create GPT boot partition ==

Install {{Pkg|parted}}
{{Cmd | apk add parted }}

Create a single UEFI boot partitions.
{{warning| This will erase all content of your {{Path|/dev/sdX}}. Make sure that you use correct device.}}

{{Cmd | parted --script /dev/sdX mklabel gpt
parted --script --align{{=}}optimal /dev/sdX mkpart ESP fat32 1MiB 100%
parted --script /dev/sdX set 1 boot on }}

== Create fat32 filesystem ==

Create a fat32 system with the name `Alpine`.

{{Cmd | mkfs.vfat -n ALPINE /dev/sdX1 }}

== Copy content of ISO image to filesystem ==

It is possible to mount the iso image and copy files with {{codeline|cp}} or {{codeline|rsync}} and it is also possible to use {{codeline|7z}} to extract content from the iso. In this example I will use the {{codeline|uniso}} utility from {{Pkg|alpine-conf}} package.

{{Cmd | mount -t vfat /dev/sdX1 /mnt
cd /mnt
uniso < /path/to/alpine-3.8.2-x86_64.iso }}

== Unmount the partition ==
Finally umount the disk
{{Cmd | cd ~ && umount /mnt}}

[[Category:Installation]]

NetworkManager

2019-07-01T14:31:44Z

PureTryOut: Created page with "NetworkManager is a program that provides automatic detection and configuration for systems to connect to networks. = Installation = NetworkManager is in the repositories and..."

NetworkManager is a program that provides automatic detection and configuration for systems to connect to networks.

= Installation =
NetworkManager is in the repositories and can be installed with the {{Pkg|networkmanager}} package. It comes with a command line interface and a curses-based interface, <code>nmcli</code> and <code>nmtui</code> respectively.

Additional interfaces:
* {{Pkg|plasma-nm}} for Plasma integration and applet
* {{Pkg|network-manager-applet}} for a GTK system tray applet

Start the daemon after installation:
<pre>rc-service networkmanager start</pre>

== Wireless networks ==
NetworkManager supports wireless networks through {{Pkg|iwd}}. After installation, enable the server and restart NetworkManager:
<pre>
rc-service iwd start
rc-service networkmanager restart
</pre>

== VPN support ==
Since version 1.16, NetworkManager has support for Wireguard[https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?id=1.16.0].

Support for other VPN types is provided by plugins. They are provided in the following packages:
* {{Pkg|networkmanager-openvpn}} for OpenVPN

LVM on LUKS

2019-06-26T13:27:24Z

PureTryOut: Improve formatting

= Introduction =

This documentation describes how to set up Alpine Linux using a logical volume (LV), that is installed in an encrypted partition. To encrypt the partition the logical volume manager (LVM) the volume group (VG) is installed in, the Device Mapper crypt (dm-crypt) module and Linux Unified Key Setup (LUKS) is used.

Note that you must install the <code>/boot/</code> directory on an unecrypted partition to boot correctly.

== Hard Disk Device Name ==

The following documentation uses the <code>vda</code> device as installation destination. If your environment uses a different device name for your hard disk, use the corresponding device names in the examples.

= Setting up Alpine Linux Using LVM on Top of a LUKS Partition =

To install Alpine Linux in logical volumes running on top of a LUKS encrypted partition, you cannot use the [[Installation|official installation]] procedure. The installation requires several manual steps you must run in the Alpine Linux Live CD environment.

== Preparing the Temporary Installation Environment ==

Before you begin to install Alpine Linux, prepare the temporary environment:

{{Note|All settings in this section apply only to the temporary environment and not to the later installed Alpine Linux on your hard disk.}}

Boot the latest Alpine Linux Installation CD. At the login prompt, use the <code>root</code> user without password to log in.

Optionally, set the keyboard language:

<pre># setup-keymap</pre>

: The default keyboard mapping is <code>us-us</code>

Configure the network interface:

<pre># setup-interfaces</pre>

: If you set a static IP address, additionally configure DNS be able to resolve host names:

<pre># setup-dns</pre>

Enable the network interface. For example:

<pre># ifup eth0</pre>

Set an apk repository and update the cache:

<pre>
# setup-apkrepos
# apk update
</pre>

Install the following packages required to set up LVM and LUKS:

<pre>
# apk add lvm2 cryptsetup e2fsprogs
</pre>

Optionally, install and start the <code>haveged</code> service for unpredictable random numbers used for encryption:

<pre>
# apk add haveged
# rc-service haveged start
</pre>

== Creating the Partition Layout ==

Linux requires an unencrypted <code>/boot/</code> partition to boot. You can assign the remaining space for the encrypted LVM physical volume (PV).

Start the <code>fdisk</code> utility to set up partitions:

<pre># fdisk /dev/vda</pre>

Create the <code>/boot/</code> partition:
* Enter <code>n</code> → <code>p</code> → <code>1</code> → <code>1</code> → <code>+100m</code> to create a new 100 MB primary partition.

Set the <code>/boot/</code> partition active:
* Enter <code>a</code> → <code>1</code>.

Create the LVM PV partition:
* Enter <code>n</code> → <code>p</code> → <code>2</code> to start creating the next partition. Press <code>Enter</code> to select the default start cylinder. Enter the size of partition. For example, <code>512m</code> for 512 MB or <code>5g</code> for 5 GB. Alternatively press <code>Enter</code> to set the maximum available size.

Set the partition type for the LVM PV:
* Enter <code>t</code> → <code>2</code> → <code>8e</code>

To verify the settings, press <code>p</code>. The output shows, for example:

<pre>
Device Boot Start End Blocks Id System
/dev/vda1 * 1 100 50368+ 83 Linux
/dev/vda2 101 10402 5192208 8e Linux LVM
</pre>

Press <code>w</code> to save the changes.

Optionally, wipe the LVM PV partition with random values:

<pre># haveged -n 0 | dd of=/dev/vda2</pre>

Depending on the size of the partition, this process can take several minutes to hours.

== Encrypting the LVM Physical Volume Partition ==

To encrypt the partition which will later contain the LVM PV:

<pre># cryptsetup luksFormat /dev/vda2</pre>

If you prefer setting an individual hashing algorithm and hashing schema:

* To run a benchmark:

<pre># cryptsetup benchmark</pre>

* To encrypt the partition using individual settings, enter, for example:

<pre># cryptsetup -v -c serpent-xts-plain64 -s 512 --hash whirlpool --iter-time 5000 --use-random luksFormat /dev/vda2</pre>

== Creating the Logical Volumes and File Systems ==

Open the LUKS partition:

<pre># cryptsetup open --type luks /dev/vda2 lvmcrypt</pre>

Create the PV on <code>/dev/vda</code>:

<pre># pvcreate /dev/mapper/lvmcrypt</pre>

Create the <code>vg0</code> LVM VG in the <code>/dev/mapper/lvmcrypt</code> PV:

<pre># vgcreate vg0 /dev/mapper/lvmcrypt</pre>

Create the LVs:

: In the following you will create a LV for the root partition. However, you can use the same command with a different LV name to create further LVs for other mount points you want to create.

* To create a 2 GB LV named <code>root</code> in the <code>vg0</code> VG:

<pre># lvcreate -L 2G vg0 -n root</pre>

* Create a 512 MB swap LV:

<pre># lvcreate -L 512M vg0 -n swap</pre>

The LVs created in the previous steps are automatically marked active. To verify, enter:

<pre># lvscan</pre>

Format the <code>root</code> LV using the ext4 file system:

<pre># mkfs.ext4 /dev/vg0/root</pre>

If you created further LVs in the previous step, create the file systems on them using the same command with the path to the LV.

Format the swap LV:

<pre># mkswap /dev/vg0/swap</pre>

== Mounting the File Systems ==

Before you can install Alpine Linux, you must mount the partitions and LVs. Mount the root LV to the <code>/mnt/</code> directory:

<pre># mount -t ext4 /dev/vg0/root /mnt/</pre>

If you created further partitions or LVs, create the mount points within the <code>/mnt/</code> directory and mount the devices.

== Installing Alpine Linux ==

In this step you will install Alpine Linux in the <code>/mnt/</code> directory, which contains the mounted file system structure:

Install Alpine Linux:

<pre># setup-disk -m sys /mnt/</pre>

The installer downloads the latest packages to install the base installation. Additionally, the installer automatically creates the entries for the mount points in the <code>fstab</code> file, which are currently mounted in the <code>/mnt/</code> directory.

{{Note|The automatic writing of the master boot record (MBR) fails in this step. You will write the MBR later manually to the disk.}}

To enable the operating system to decrypt the PV at boot time, create the <code>/mnt/etc/crypttab</code> file. Enter the following line into the file to decrypt the <code>/dev/vda2</code> partition using the <code>luks</code> module and map it to the <code>lvmcrypt</code> name:

<pre>lvmcrypt /dev/vda2 none luks</pre>

The swap LV is not automatically added to the <code>fstab</code> file. To add it manually, add the following line to the <code>/mnt/etc/fstab</code> file:

<pre>/dev/vg0/swap swap swap defaults 0 0</pre>

Edit the <code>/mnt/etc/mkinitfs/mkinitfs.conf</code> file and append the <code>cryptsetup</code> module to the <code>features</code> parameter:

<pre>features="ata base ide scsi usb virtio ext4 lvm cryptsetup"</pre>

{{Note|Alpine Linux uses the <code>en-us</code> keyboard mapping by default when prompting for the password to decrypt the partition at boot time. If you changed the keyboard mapping in the temporary environment and want to use it at the boot password prompt, be sure to also add the <code>keymap<code> feature to the list above.}}

Rebuild the initial RAM disk:

<pre># mkinitfs -c /mnt/etc/mkinitfs/mkinitfs.conf -b /mnt/ $(ls /mnt/lib/modules/)</pre>

The command uses the settings from the <code>mkinitfs.conf</code> file set in the <code>-c</code> parameter to generate the RAM disk. The command is executed in the <code>/mnt/</code> directory and the RAM disk is generated using the modules for the installed kernel. Without setting the kernel version using the <code>$(ls /mnt/lib/modules/</code>) option, <code>mkinitfs</code> tries to generate the RAM disk using the kernel version installed in the temporary environment, which can differ from the latest one installed by the <code>setup-disk</code> utility.

== Installing a bootloader ==
=== Syslinux ===

Format the <code>/dev/vda1</code> device for the <code>/boot/</code> partition using the ext4 file system:

<pre># mkfs.ext4 /dev/vda1</pre>

Create <code>/mnt/boot/</code> directory and mount the <code>/dev/vda1</code> partition in this directory:

<pre>
# mkdir /mnt/boot/
# mount -t ext4 /dev/vda1 /mnt/boot/
</pre>

Install the Syslinux package:

<pre># apk add syslinux</pre>

Edit the <code>/mnt/etc/update-extlinux.conf</code> file and append the following kernel options to the <code>default_kernel_opts</code> parameter:

<pre>default_kernel_opts="... cryptroot=/dev/vda2 cryptdm=lvmcrypt"</pre>

: The <code>cryptroot</code> parameter sets the name of the device that contains the root file system. The <code>cryptdm</code> parameter sets the name of the mapping previously set in the <code>crypttab</code> file.

Because the <code>update-extlinux</code> utility operators only on the <code>/boot/</code> directory, temporarily change the root to the <code>/mnt/</code> directory and update the boot loader configuration:

<pre>
# chroot /mnt/
# update-extlinux
# exit
</pre>

: Ignore the errors the <code>update-extlinux</code> utility displays.

Write the MBR to the <code>/dev/vda</code> device:

<pre># dd bs=440 count=1 conv=notrunc if=/mnt/usr/share/syslinux/mbr.bin of=/dev/vda</pre>

=== Grub on EFI ===

Format the <code>/dev/vda1</code> device for the <code>/boot/</code> partition using the FAT32 file system:

<pre>
# apk add dosfstools
# mkfs.fat -F32 /dev/vda1
</pre>

Create <code>/mnt/boot/</code> directory and mount the <code>/dev/vda1</code> partition in this directory:

<pre>
# mkdir /mnt/boot/
# mount /dev/vda1 /mnt/boot/
</pre>

Edit the <code>/mnt/etc/default/grub</code> file and add the following kernel options to the <code>GRUB_CMDLINE_LINUX_DEFAULT</code> parameter:

<pre>cryptroot=/dev/vda2 cryptdm=lvmcrypt</pre>

The <code>cryptroot</code> parameter sets the name of the device that contains the root file system. The <code>cryptdm</code> parameter sets the name of the mapping previously set in the <code>crypttab</code> file.

Mount the required filesystems for the Grub EFI installer to the installation:

<pre>
# mount -t proc /proc /mnt/proc
# mount --rbind /dev /mnt/dev
# mount --make-rslave /mnt/dev
</pre>

Then chroot in and use <code>grub-install</code> to install Grub.

<pre>
# (chroot) chroot /mnt
# (chroot) apk add grub grub-efi efibootmgr
# (chroot) grub-install --target=x86_64-efi --efi-directory=/boot
# (chroot) grub-mkconfig -o /boot/grub/grub.cfg
# (chroot) exit
</pre>

== Unmounting the Volumes and Partitions ==

Umount <code>/mnt/boot/</code> and <code>/mnt/</code>:

<pre>
# umount /mnt/boot/
# umount /mnt/
</pre>

{{Note|If you mounted further partitions or LVs below <code>/mnt/</code>, you must first unmount all of them before you can unmount <code>/mnt/</code>.}}

Disable the swap partition:

<pre># swapoff -a</pre>

Deactivate the VG:

<pre># vgchange -a n</pre>

Close the <code>lvmcrypt</code> device:

<pre># cryptsetup luksClose lvmcrypt</pre>

Reboot the system:

<pre># reboot</pre>

= Troubleshooting =

== General Procedure ==

In case your system fails to boot, you can verify the settings and fix incorrect configurations.

Reboot and do the steps in [[#Preparing_the_Temporary_Installation_Environment|Prepare the temporary installation environment]] again.

Activate the VGs:

<pre># vgchange -a y</pre>

[[#Mounting_the_File_Systems|Mount the file systems]]

Verify that you run the steps described in the [[#Installing_Alpine_Linux|Installing Alpine Linux]] section correctly. Update the configuration if necessary.

[[#Unmounting_the_Volumes_and_Partitions|Unmount the volumes and partitions]]

= Hardening =

* To harden, you should disable DMA[https://old.iseclab.org/papers/acsac2012dma.pdf] and install a hardened version of AES (TRESOR[https://www1.informatik.uni-erlangen.de/tresor] or Loop-Amnesia[http://moongate.ydns.eu/amnesia.html]) since by default cryptsetup with luks uses AES by default.
* Disable DMA in the BIOS and set the password for the BIOS according to Wikipedia.[https://en.wikipedia.org/wiki/DMA_attack]
* Blacklist kernel modules that use DMA and any unused expansion modules (FireWire, CardBus, ExpressCard, Thunderbolt, USB 3.0, PCI Express and hotplug modules) that use DMA.

[[Category:Storage]]
[[Category:Security]]