Alpine Linux - Recent changes [en]

User:Sama pama

Sama pama — Sat, 25 Apr 2026 19:55:13 GMT

User account Sama pama was created

User:HongTenison

HongTenison — Fri, 24 Apr 2026 16:21:34 GMT

← Older revision		Revision as of 16:21, 24 April 2026
Line 1:		Line 1:
	Welcome for the ~~foremost~~ electronic repository meant to ~~aid~~ professionals obtain ~~benchmarks~~ and ~~obtain standards~~ freed from the ~~usual~~ administrative hurdles. Our ~~System~~ was ~~Launched~~ by a collective of structural engineers, ~~complex~~ translators, and Search engine ~~optimization professionals~~ who ~~identified~~ a ~~huge~~ hole in the accessibility of ~~critical~~ industrial documentation. We ~~believe~~ that ~~security~~ and compliance ~~really should not~~ be locked ~~driving~~ prohibitive paywalls, ~~Which~~ is ~~the reason~~ we’ve built a streamlined motor ~~that can~~ assist you ~~discover requirements~~ from ~~every key Global body~~, ~~including~~ ISO, ASTM, AS/NZS, ~~along with~~ the IEC.<br><br>Our mission ~~would~~ be to empower the worldwide engineering ~~Local~~ community. Whether you are ~~taking care of~~ a ~~complex~~ construction job in South Africa or optimizing a ~~production~~ line in Southeast Asia, our database ~~lets~~ you ~~obtain expectations which are~~ important for operational integrity. We ~~focus on offering~~ deep-dive ~~complex~~ insights into ~~fireplace~~-rated glass ~~technical specs~~, maritime security protocols, and the ~~most up-to-date~~ in electrotechnical dependability.<br><br>By ~~choosing~~ our ~~platform~~ to ~~uncover standards~~, you are signing up for a network of above ~~500~~,000 ~~month-to-month consumers~~ who prioritize precision and technical ~~precision~~. We don't just ~~offer~~ a ~~destination~~ to ~~obtain specifications cost-~~free; we ~~provide a comprehensive~~ ecosystem ~~that includes complex~~ guides, cross-reference tables for ~~Intercontinental~~ equivalents (like BS EN vs. JIS), and the ~~latest~~ updates on "~~environmentally~~ friendly" ~~constructing~~ codes. Our ~~dedication~~ to large-velocity accessibility and ~~details~~-~~driven~~ precision would make us the ~~premier choice~~ for the ~~fashionable~~ digital engineer.		Welcome for the primary electronic repository meant to support professionals obtain expectations and download requirements freed from the standard administrative hurdles. Our platform was Established by a collective of structural engineers, specialized translators, and Search engine marketing experts who acknowledged a massive hole while in the accessibility of essential industrial documentation. We feel that safety and compliance shouldn't be locked guiding prohibitive paywalls, which is why we’ve built a streamlined motor to assist you obtain expectations from each main Intercontinental system, together with ISO, ASTM, AS/NZS, and also the IEC.<br><br>Our mission should be to empower the worldwide engineering community. Whether you are controlling a posh construction job in South Africa or optimizing a manufacturing line in Southeast Asia, our database permits you to download specifications that happen to be important for operational integrity. We specialise in delivering deep-dive technical insights into fire-rated glass specifications, maritime security protocols, and the newest in electrotechnical dependability.<br><br>By deciding upon our System to discover specifications, you are signing up for a network of above five hundred,000 monthly end users who prioritize precision and technical accuracy. We don't just provide a location to down load standards free of charge; we offer an extensive ecosystem showcasing technological guides, cross-reference tables for international equivalents (like BS EN vs. JIS), and the most up-to-date updates on "eco-friendly" creating codes. Our motivation to large-velocity accessibility and data-pushed precision would make us the Leading option for the modern digital engineer.

Infinitime

WhyNotHugo — Thu, 23 Apr 2026 16:06:31 GMT

Create page (lists build dependencies)

New page

[https://infinitime.io/ InfiniTime] is an open source firmware for the Pinetime smartwatch written in C++ and based on [https://www.freertos.org/ FreeRTOS].

All dependencies for compiling the firmware are packaged in the Alpine repositories, and can be installed via:

<pre>
apk add -t .infinitime-dev \
cmake \
gcc-arm-none-eabi \
lv_font_conv \
nrf5-sdk \
py3-cbor2 \
py3-cryptography \
py3-intelhex
</pre>

ZFS

John3-16 — Thu, 23 Apr 2026 01:36:49 GMT

Style/grammar amendments.

← Older revision		Revision as of 01:36, 23 April 2026
Line 55:		Line 55:
	== Maintenance ==		== Maintenance ==

	On Alpine Linux, there in no cron/script provided to scrub (and eventually trim) your pool(s) on a regular basis, like in other Linux distributions.		On Alpine Linux, there is no cron/script provided to scrub (and eventually trim) your pool(s) on a regular basis, like in other Linux distributions.

	=== Scrub ===		=== Scrub ===
Line 114:		Line 114:
	Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/scrub}}		Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/scrub}}

	It is recommended to scrub regularly to ~~assure~~ your pool(s) and data are in good shape. In our example, the scrub script will be launched once a month, on the 2nd Sunday of the month using [[cron]].		It is recommended to scrub regularly to ensure that your pool(s) and data are in good shape. In our example, the scrub script will be launched once a month, on the 2nd Sunday of the month using [[cron]].

	Edit your crontabs using the command: {{cmd\|# crontab -e}}		Edit your crontabs using the command: {{cmd\|# crontab -e}}
Line 120:		Line 120:
	and add these 2 lines:		and add these 2 lines:
	<pre>		<pre>
	# ~~zfs~~ scrub the 2nd Sunday of every month		# ZFS scrub the 2nd Sunday of every month
	24 0 8-14 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/scrub ]; then /usr/libexec/zfs/scrub; fi		24 0 8-14 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/scrub ]; then /usr/libexec/zfs/scrub; fi
	</pre>		</pre>
Line 195:		Line 195:
	Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/trim}}		Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/trim}}

	It is recommended to trim regularly to ensure that your pool(s) and data are in good shape. In our example, the trim script will be launched once a month, on the 1st Sunday of the month using [[cron]]		It is recommended to trim regularly to ensure that your pool(s) and data are in good shape. In our example, the trim script will be launched once a month, on the 1st Sunday of the month using [[cron]].

	Edit your crontabs using the command: {{cmd\|# crontab -e}}		Edit your crontabs using the command: {{cmd\|# crontab -e}}
	and add these 2 lines:		and add these 2 lines:
	<pre>		<pre>
	# ~~zfs~~ trim the 1st Sunday of every month		# ZFS trim the 1st Sunday of every month
	24 0 1-7 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/trim ]; then /usr/libexec/zfs/trim; fi		24 0 1-7 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/trim ]; then /usr/libexec/zfs/trim; fi
	</pre>		</pre>

User:MarthaWestall80

MarthaWestall80 — Wed, 22 Apr 2026 09:04:47 GMT

User account MarthaWestall80 was created

User:Margot6559

Abuse filter — Wed, 22 Apr 2026 06:16:17 GMT

Abuse filter blocked Margot6559 with an expiration time of indefinite (account creation disabled, cannot edit own talk page) Automatically blocked by abuse filter. Description of matched rule: We are not interested in gambling sites, thank you.

User:Margot6559

Abuse filter — Wed, 22 Apr 2026 06:16:17 GMT

Abuse filter blocked the autopromotion of Margot6559 for a period of 5 days Autopromotion automatically delayed by abuse filter. Rule description: We are not interested in gambling sites, thank you.

User:Margot6559

Margot6559 — Wed, 22 Apr 2026 03:11:32 GMT

User account Margot6559 was created

User:HongTenison

HongTenison — Tue, 21 Apr 2026 17:09:11 GMT

← Older revision		Revision as of 17:09, 21 April 2026
Line 1:		Line 1:
	Welcome to the ~~primary digital~~ repository ~~built~~ to ~~enable industry experts find criteria~~ and ~~down load requirements free of~~ the usual administrative hurdles. Our System was ~~Started~~ by a collective of structural engineers, ~~specialized~~ translators, and Search engine ~~optimisation experts~~ who ~~acknowledged an enormous gap from~~ the accessibility of ~~important~~ industrial documentation. We ~~think~~ that ~~protection~~ and compliance should not be locked ~~guiding~~ prohibitive paywalls, Which ~~explains why~~ we’ve ~~designed~~ a streamlined ~~engine to help~~ you ~~obtain benchmarks~~ from ~~each~~ key ~~international human~~ body, ~~which includes~~ ISO, ASTM, AS/NZS, ~~and~~ the IEC.<br><br>Our mission ~~is usually~~ to empower the ~~global~~ engineering ~~Group~~. Whether you are ~~managing~~ a complex ~~building undertaking~~ in South Africa or optimizing a ~~producing~~ line in Southeast Asia, our database ~~permits~~ you ~~to down load standards~~ which ~~can be~~ important for operational integrity. We ~~concentrate~~ on ~~giving~~ deep-dive ~~technical~~ insights into fireplace-rated glass ~~specifications~~, maritime ~~protection~~ protocols, and the ~~newest~~ in electrotechnical ~~trustworthiness~~.<br><br>By ~~picking~~ our ~~System~~ to ~~seek out expectations~~, you are ~~joining~~ a ~~community~~ of ~~more than~~ 500,000 ~~regular buyers~~ who prioritize precision and ~~technological~~ precision. We don't just ~~provide~~ a ~~place~~ to ~~download expectations~~ free ~~of charge~~; we provide a comprehensive ecosystem that includes ~~specialized~~ guides, cross-reference tables for ~~Global~~ equivalents (like BS EN vs. JIS), and the ~~most recent~~ updates on "~~eco-~~friendly" ~~setting up~~ codes. Our ~~commitment~~ to large-~~pace~~ accessibility and ~~info~~-~~pushed accuracy helps~~ make us the ~~Leading option~~ for the fashionable digital engineer.		Welcome for the foremost electronic repository meant to aid professionals obtain benchmarks and obtain standards freed from the usual administrative hurdles. Our System was Launched by a collective of structural engineers, complex translators, and Search engine optimization professionals who identified a huge hole in the accessibility of critical industrial documentation. We believe that security and compliance really should not be locked driving prohibitive paywalls, Which is the reason we’ve built a streamlined motor that can assist you discover requirements from every key Global body, including ISO, ASTM, AS/NZS, along with the IEC.<br><br>Our mission would be to empower the worldwide engineering Local community. Whether you are taking care of a complex construction job in South Africa or optimizing a production line in Southeast Asia, our database lets you obtain expectations which are important for operational integrity. We focus on offering deep-dive complex insights into fireplace-rated glass technical specs, maritime security protocols, and the most up-to-date in electrotechnical dependability.<br><br>By choosing our platform to uncover standards, you are signing up for a network of above 500,000 month-to-month consumers who prioritize precision and technical precision. We don't just offer a destination to obtain specifications cost-free; we provide a comprehensive ecosystem that includes complex guides, cross-reference tables for Intercontinental equivalents (like BS EN vs. JIS), and the latest updates on "environmentally friendly" constructing codes. Our dedication to large-velocity accessibility and details-driven precision would make us the premier choice for the fashionable digital engineer.

User:WendiBorelli643

WendiBorelli643 — Tue, 21 Apr 2026 08:36:25 GMT

User account WendiBorelli643 was created

ZFS

John3-16 — Tue, 21 Apr 2026 04:23:30 GMT

Style/grammar amendments.

← Older revision		Revision as of 04:23, 21 April 2026
Line 65:		Line 65:
	A scrub is split into two parts: metadata scanning and block scrubbing. The metadata scanning sorts blocks into large sequential ranges which can then be read much more efficiently from disk when issuing the scrub I/O.		A scrub is split into two parts: metadata scanning and block scrubbing. The metadata scanning sorts blocks into large sequential ranges which can then be read much more efficiently from disk when issuing the scrub I/O.

	This script is taken from ~~debian zfs~~ scripts. It is used to list the pools, ~~make~~ sure they are online, and no scrub is being done at the time. The contents of the script placed at {{path\|/usr/libexec/zfs/scrub}} are as follows:{{cat\|/usr/libexec/zfs/scrub\|<nowiki>#!/bin/sh -eu		This script is taken from Debian ZFS scripts. It is used to list the pools, making sure that they are online and that no scrub is being done at the time. The contents of the script placed at {{path\|/usr/libexec/zfs/scrub}} are as follows:{{cat\|/usr/libexec/zfs/scrub\|<nowiki>#!/bin/sh -eu

	# directly exit successfully when zfs module is not loaded		# directly exit successfully when zfs module is not loaded
Line 114:		Line 114:
	Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/scrub}}		Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/scrub}}

	It is recommended to scrub regularly to assure your pool(s) and ~~datas~~ are in good shape. In our example, the scrub script will be launched once a month, on the 2nd Sunday of the month using [[cron]].		It is recommended to scrub regularly to assure your pool(s) and data are in good shape. In our example, the scrub script will be launched once a month, on the 2nd Sunday of the month using [[cron]].

	Edit your crontabs using the command: {{cmd\|# crontab -e}}		Edit your crontabs using the command: {{cmd\|# crontab -e}}
Line 128:		Line 128:
	The command {{ic\|zpool trim}} initiates an immediate on-demand TRIM operation for all of the free space in a pool. This operation informs the underlying storage devices of all blocks in the pool which are no longer allocated and allows thinly provisioned devices to reclaim the space.		The command {{ic\|zpool trim}} initiates an immediate on-demand TRIM operation for all of the free space in a pool. This operation informs the underlying storage devices of all blocks in the pool which are no longer allocated and allows thinly provisioned devices to reclaim the space.

	A manual on-demand TRIM operation can be initiated irrespective of the [https://openzfs.github.io/openzfs-docs/man/v2.2/7/zpoolprops.7.html#autotrim autotrim] pool property setting. The link shows the types of ~~vdev~~ devices ~~which~~ can be trimmed.		A manual on-demand TRIM operation can be initiated irrespective of the [https://openzfs.github.io/openzfs-docs/man/v2.2/7/zpoolprops.7.html#autotrim autotrim] pool property setting. The link shows the types of VDEV devices that can be trimmed.

	This script is taken from ~~debian zfs~~ scripts. It is used to list the pools, ~~make~~ sure they are online, ~~build~~ only with ~~NVME ssd~~ drive(s) and no trim is being done at the time. The contents of the script placed at {{path\|/usr/libexec/zfs/trim}} is as follows:{{cat\|/usr/libexec/zfs/trim\|<nowiki>#!/bin/sh -eu		This script is taken from Debian ZFS scripts. It is used to list the pools, making sure that they are online, built only with NVMe SSD drive(s) and that no trim is being done at the time. The contents of the script placed at {{path\|/usr/libexec/zfs/trim}} are as follows:{{cat\|/usr/libexec/zfs/trim\|<nowiki>#!/bin/sh -eu

	# directly exit successfully when zfs module is not loaded		# directly exit successfully when zfs module is not loaded
Line 195:		Line 195:
	Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/trim}}		Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/trim}}

	It is recommended to trim regularly to ~~assure~~ your pool(s) and ~~datas~~ are in good shape. So the trim script will be launched once a month, on the 1st ~~sunday~~ of the month using [[cron]]		It is recommended to trim regularly to ensure that your pool(s) and data are in good shape. In our example, the trim script will be launched once a month, on the 1st Sunday of the month using [[cron]]

	Edit your crontabs using the command: {{cmd\|# crontab -e}}		Edit your crontabs using the command: {{cmd\|# crontab -e}}
	and add these 2 lines		and add these 2 lines:
	<pre>		<pre>
	# zfs trim the ~~first sunday~~ of every month		# zfs trim the 1st Sunday of every month
	24 0 1-7 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/trim ]; then /usr/libexec/zfs/trim; fi		24 0 1-7 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/trim ]; then /usr/libexec/zfs/trim; fi
	</pre>		</pre>

System Disk Mode

WhyNotHugo — Mon, 20 Apr 2026 16:08:53 GMT

Data Disk Mode

WhyNotHugo — Mon, 20 Apr 2026 16:08:23 GMT

User:BlueKnigh

BlueKnigh — Mon, 20 Apr 2026 13:12:05 GMT

User account BlueKnigh was created

ZFS

John3-16 — Sun, 19 Apr 2026 03:59:10 GMT

Style/grammar amendments.

User:AidanHubbs49508

AidanHubbs49508 — Sat, 18 Apr 2026 23:52:55 GMT

User account AidanHubbs49508 was created

User:Jsm

Jsm — Sat, 18 Apr 2026 20:29:29 GMT

User account Jsm was created

User:BrittneyCardenas

BrittneyCardenas — Sat, 18 Apr 2026 12:06:56 GMT

User account BrittneyCardenas was created

User:DeclanTudawali

DeclanTudawali — Sat, 18 Apr 2026 10:07:34 GMT

User account DeclanTudawali was created

Upgrading Qt

PureTryOut — Sat, 18 Apr 2026 10:01:07 GMT

← Older revision		Revision as of 10:01, 18 April 2026
Line 6:		Line 6:
	* kguiaddons (for plasmashell)		* kguiaddons (for plasmashell)
	* libkscreen (for display configuration)		* libkscreen (for display configuration)
			* powerdevil (for power management KCM)
	* pyside6 (all it's users need to be rebuild as well)		* pyside6 (all it's users need to be rebuild as well)

Draft Release Notes for Alpine 3.24.0

Fossdd — Sat, 18 Apr 2026 09:03:21 GMT

Significant package removals: librewolf

← Older revision		Revision as of 09:03, 18 April 2026
Line 102:		Line 102:

	{{Note\|TODO}}		{{Note\|TODO}}

			=== librewolf ===

			{{Note\|TODO https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/100935#note_603275}}

	<hr><center>[[Release Notes for Alpine 3.23.0\|← Previous page: Release Notes for Alpine 3.23.0]]</center>		<hr><center>[[Release Notes for Alpine 3.23.0\|← Previous page: Release Notes for Alpine 3.23.0]]</center>

	[[Category:News]]		[[Category:News]]

User:LudieTew52

LudieTew52 — Sat, 18 Apr 2026 02:44:12 GMT

User account LudieTew52 was created

Nut-ups

Ingrate one — Fri, 17 Apr 2026 08:25:39 GMT

Add information for setup of network server/clients includes the following configuration files nut.conf, upsd.users and mupsmon.conf. Finally to perform Live shutdown to hosts with matching users and ups fields.

@@ Line 43: / Line 43: @@
 To instruct NUT to make the UPS status available on the network, create the {{Path|/etc/nut/nut.conf}} file with content as follows: {{Cat|/etc/nut/nut.conf|<nowiki>MODE=netserver</nowiki>}}
 The content of {{Path|/etc/nut/ups.conf}} defines the name (in square brackets), the driver used to communicate with the UPS, and the port. For USB-attached UPSs, it's almost always going to be a driver of ''usbhid-ups'' and a port of ''auto''. Make and model should not make any difference here provided that it is a USB-attached UPS. Create the file {{Path|/etc/nut/ups.conf}} with content as follows: {{Cat|/etc/nut/ups.conf|<nowiki>[SmartUPS_1000]
      driver = usbhid-ups
@@ Line 50: / Line 52: @@
 {{Tip| Replace 0.0.0.0 with the network address of a specific interface if none of the interfaces are appropriate for your situation.}}
 === Configure udev rules ===
@@ Line 79: / Line 124: @@
 [[#Verifying running state|Verify the running state]] before proceeding to configure the automatic startup of the {{ic|nut-upsd}}. If everything looks good, go ahead and set the service to auto-start when the system is booted:{{Cmd|# rc-update add nut-upsd
    * service nut-upsd added to runlevel default}}
 == Using NUT ==

User:Kirill

Kirill — Thu, 16 Apr 2026 09:51:28 GMT

User account Kirill was created

User:GuGuan123

GuGuan123 — Wed, 15 Apr 2026 23:14:10 GMT

User account GuGuan123 was created

Installing Alpine Linux on OrangePi RV2

Aarch0x40 — Wed, 15 Apr 2026 21:33:59 GMT

← Older revision		Revision as of 21:33, 15 April 2026
(One intermediate revision by the same user not shown)
Line 2:		Line 2:
	[[Main Page]] > [[:Category:Architectures\|Architectures]] > [[Riscv64]] > Installing Alpine Linux on OrangePi RV2		[[Main Page]] > [[:Category:Architectures\|Architectures]] > [[Riscv64]] > Installing Alpine Linux on OrangePi RV2
	<br /><br />		<br /><br />
	{{Warning\|The contributors to the Alpine Linux project are not responsible for any damage/loss experienced by using the following guide. This article is provided as a general reference. It is assumed that the implementer will have the knowledge and ability to close the gap between what is described here and their specific setup.}}		{{Warning\|The contributors to the Alpine Linux project are not responsible for any damage/loss experienced by using the following guide. This article is provided as a general reference. It is assumed that the implementer will have the knowledge and ability to close the gap between what is described here and their specific setup.
			<br/><br/>Implementers of this guide should consider the result development / alpha quality.}}

	The [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-RV2.html OrangePi RV2] is a credit-card sized development board with a Ky X1 8-Core SoC. The Ky X1 is for all intents and purposes a SpacemiT K1 SoC. The remainder of this guide is more likely to use the terms SpacemiT or K1 as is prevalent throughout the Linux community. Please understand that these terms all refer to the same RISC-V ISA implementation.		The [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-RV2.html OrangePi RV2] is a credit-card sized development board with a Ky X1 8-Core SoC. The Ky X1 is for all intents and purposes a SpacemiT K1 SoC. The remainder of this guide is more likely to use the terms SpacemiT or K1 as is prevalent throughout the Linux community. Please understand that these terms all refer to the same RISC-V ISA implementation.

User:KlaudiaC90

KlaudiaC90 — Wed, 15 Apr 2026 20:26:34 GMT

User account KlaudiaC90 was created

Template:AlpineLatest

Ncopa — Wed, 15 Apr 2026 11:59:25 GMT

← Older revision		Revision as of 11:59, 15 April 2026
Line 1:		Line 1:
	<noinclude>{{Template}}		<noinclude>{{Template}}
	</noinclude>3.23.3		</noinclude>3.23.4

PipeWire

Prabuanand — Wed, 15 Apr 2026 10:47:04 GMT

added wikilink

← Older revision		Revision as of 10:47, 15 April 2026
Line 128:		Line 128:
	==== Without PAM ====		==== Without PAM ====

	If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. If this is the case, add your user to the {{Ic\|rtkit}} group. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.		If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. If this is the case, [[Setting_up_a_new_user#Group_management\|add your user]] to the {{Ic\|rtkit}} group. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.

	==== Using PAM ====		==== Using PAM ====

	Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included which applies to sessions started via PAM for members of the {{Ic\|pipewire}} group. If this is the case, add your user to the {{Ic\|pipewire}} group.		Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included which applies to sessions started via PAM for members of the {{Ic\|pipewire}} group. If this is the case, [[Setting_up_a_new_user#Group_management\|add your user]] to the {{Ic\|pipewire}} group.

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.

User:HongTenison

HongTenison — Wed, 15 Apr 2026 03:32:52 GMT

← Older revision		Revision as of 03:32, 15 April 2026
Line 1:		Line 1:
	Welcome ~~into~~ the ~~major~~ digital repository built to ~~assistance specialists uncover~~ criteria and ~~download standards~~ free of the ~~standard~~ administrative hurdles. Our ~~platform~~ was ~~founded~~ by a collective of structural engineers, ~~technological~~ translators, and Search engine optimisation ~~professionals~~ who ~~regarded a huge hole while in~~ the accessibility of ~~significant~~ industrial documentation. We think that ~~security~~ and compliance ~~really~~ should not be locked ~~behind~~ prohibitive paywalls, ~~And that's~~ why we’ve ~~crafted~~ a streamlined engine ~~that can assist~~ you ~~locate requirements~~ from each ~~individual~~ key ~~Worldwide overall~~ body, ~~such as~~ ISO, ASTM, AS/NZS, ~~along with~~ the IEC.<br><br>Our mission is usually to empower the global engineering ~~Local community~~. Whether you are ~~controlling~~ a ~~posh development job~~ in South Africa or optimizing a producing line in Southeast Asia, our ~~databases enables~~ you to down load standards which can be important for operational integrity. We ~~specialise in furnishing~~ deep-dive ~~technological~~ insights into ~~fire~~-rated glass ~~technical specs~~, maritime ~~safety~~ protocols, and the ~~most recent~~ in electrotechnical ~~reliability~~.<br><br>By picking ~~out~~ our System to ~~uncover standards~~, ~~that~~ you are joining a ~~network~~ of ~~above~~ 500,000 regular ~~customers~~ who prioritize precision and ~~complex~~ precision. We don't just ~~offer~~ a ~~destination~~ to ~~obtain specifications cost-~~free; we ~~offer~~ a comprehensive ecosystem ~~showcasing technological~~ guides, cross-reference tables for Global equivalents (like BS EN vs. JIS), and the most recent updates on "~~environmentally~~ friendly" ~~making~~ codes. Our ~~determination~~ to large-~~velocity~~ accessibility and ~~knowledge~~-~~driven precision will~~ make us the ~~premier choice~~ for the ~~modern~~ digital engineer.		Welcome to the primary digital repository built to enable industry experts find criteria and down load requirements free of the usual administrative hurdles. Our System was Started by a collective of structural engineers, specialized translators, and Search engine optimisation experts who acknowledged an enormous gap from the accessibility of important industrial documentation. We think that protection and compliance should not be locked guiding prohibitive paywalls, Which explains why we’ve designed a streamlined engine to help you obtain benchmarks from each key international human body, which includes ISO, ASTM, AS/NZS, and the IEC.<br><br>Our mission is usually to empower the global engineering Group. Whether you are managing a complex building undertaking in South Africa or optimizing a producing line in Southeast Asia, our database permits you to down load standards which can be important for operational integrity. We concentrate on giving deep-dive technical insights into fireplace-rated glass specifications, maritime protection protocols, and the newest in electrotechnical trustworthiness.<br><br>By picking our System to seek out expectations, you are joining a community of more than 500,000 regular buyers who prioritize precision and technological precision. We don't just provide a place to download expectations free of charge; we provide a comprehensive ecosystem that includes specialized guides, cross-reference tables for Global equivalents (like BS EN vs. JIS), and the most recent updates on "eco-friendly" setting up codes. Our commitment to large-pace accessibility and info-pushed accuracy helps make us the Leading option for the fashionable digital engineer.

PipeWire

Prabuanand — Wed, 15 Apr 2026 02:47:32 GMT

added the instruction to add users to the group

← Older revision		Revision as of 02:47, 15 April 2026
(One intermediate revision by the same user not shown)
Line 128:		Line 128:
	==== Without PAM ====		==== Without PAM ====

	If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.		If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. If this is the case, add your user to the {{Ic\|rtkit}} group. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.

	==== Using PAM ====		==== Using PAM ====

	Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included~~. This configuration~~ applies to sessions started via PAM for members of the {{Ic\|pipewire}} group.		Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included which applies to sessions started via PAM for members of the {{Ic\|pipewire}} group. If this is the case, add your user to the {{Ic\|pipewire}} group.

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.

User:Alex Neumann

Alex Neumann — Tue, 14 Apr 2026 23:43:53 GMT

User account Alex Neumann was created

PipeWire

WhyNotHugo — Tue, 14 Apr 2026 16:50:14 GMT

Realtime scheduling: The details for configuring limits apply to the PAM configuration, not the rtkit configuration.

← Older revision		Revision as of 16:50, 14 April 2026
Line 124:		Line 124:
	Realtime scheduling will increase certain threads priorities to assist with low latency audio processing. By default, PipeWire tries to enable realtime scheduling with the [https://docs.pipewire.org/page_module_rt.html rt module].		Realtime scheduling will increase certain threads priorities to assist with low latency audio processing. By default, PipeWire tries to enable realtime scheduling with the [https://docs.pipewire.org/page_module_rt.html rt module].

	~~==== Option1 ====~~		This can be done in one of two ways: via {{Pkg\|rtkit}} or via PAM.

	~~Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], when you have a [[~~PAM~~]] login session, you should add your user to the {{Ic\|pipewire}} group.~~		==== Without PAM ====

	~~==== option2 ====~~		If the current session is not using [[PAM]] and the system [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}. Only users in the {{Ic\|rtkit}} group shall be allowed to increase priorities via this mechanism.

	~~If you don't have [[~~PAM~~]] but [[D-Bus]] is available, the rt module will try to use {{Pkg\|rtkit}}; if this is the case, add your user to the {{Ic\|rtkit}} group.~~		==== Using PAM ====

			Since [https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.66 PipeWire 0.3.66], a [[PAM]] configuration is included. This configuration applies to sessions started via PAM for members of the {{Ic\|pipewire}} group.

	The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. ~~You may want to adjust settings for parameters like~~ <var>rt.prio</var>~~, if required~~. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.		The default system wide settings are defined in {{Path\|/etc/security/limits.d/25-pw-rlimits.conf}}. Parameters such as <var>rt.prio</var> may be adapted according to each use case as necessary. Alternatively, it can be set at [https://docs.pipewire.org/page_module_rt.html user level] within the ceiling set by the system's rlimits.

	{{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [		{{Cat\|~/.config/pipewire/pipewire.conf.d/my-rt-args.conf\|<nowiki>context.modules = [

User:GarrettD49

GarrettD49 — Tue, 14 Apr 2026 15:05:45 GMT

User account GarrettD49 was created

User:DanieleZsq

DanieleZsq — Tue, 14 Apr 2026 14:21:55 GMT

User account DanieleZsq was created

Audacity

Alpinelover420 — Tue, 14 Apr 2026 10:19:25 GMT

Integration with FFmpeg: better wording

← Older revision		Revision as of 10:19, 14 April 2026
Line 4:		Line 4:

	== Integration with FFmpeg ==		== Integration with FFmpeg ==
	Audacity optionally supports integration with some versions of FFmpeg for working with additional audio formats. According to official support pages<small>[https://support.audacityteam.org/basics/installing-ffmpeg]</small> as of {{#time:F j, Y\|20260413030000}}, Audacity 3.2+ ~~supports at most~~ version 60 of libavformat. If you are using such a version of Audacity, the libraries installed by the {{Pkg\|ffmpeg}} package will be incompatible with your installation. You will need to install {{Pkg\|ffmpeg6-libavformat}}.		Audacity optionally supports integration with some versions of FFmpeg for working with additional audio formats. According to official support pages<small>[https://support.audacityteam.org/basics/installing-ffmpeg]</small> as of {{#time:F j, Y\|20260413030000}}, Audacity 3.2+ is compatible with version 60 of libavformat. If you are using such a version of Audacity, the libraries installed by the {{Pkg\|ffmpeg}} package will be incompatible with your installation. You will need to install {{Pkg\|ffmpeg6-libavformat}}.

	== See also ==		== See also ==

Audacity

Alpinelover420 — Tue, 14 Apr 2026 10:18:03 GMT

Drafted page for Audacity to provide (hopefully) helpful information about using it with FFmpeg

New page

{{Draft|The author believes this information is accurate and would like comments on whether this notice can be removed.}}

Audacity is a free and open-source audio editing and recording application. It is available on the Alpine Linux community repository as {{Pkg|audacity}}.

== Integration with FFmpeg ==
Audacity optionally supports integration with some versions of FFmpeg for working with additional audio formats. According to official support pages<small>[https://support.audacityteam.org/basics/installing-ffmpeg]</small> as of {{#time:F j, Y|20260413030000}}, Audacity 3.2+ supports at most version 60 of libavformat. If you are using such a version of Audacity, the libraries installed by the {{Pkg|ffmpeg}} package will be incompatible with your installation. You will need to install {{Pkg|ffmpeg6-libavformat}}.

== See also ==
* Official Audacity links
** [https://www.audacityteam.org/ Website]
** [https://manual.audacityteam.org/ Manual]
** [https://support.audacityteam.org/ Support]
*** [https://support.audacityteam.org/basics/installing-ffmpeg Installing FFmpeg]
* [https://wiki.archlinux.org/title/Audacity Audacity on the ArchWiki]
* [https://wiki.gentoo.org/wiki/Audacity Audacity on the GentooWiki]

[[Category:Software]]
[[Category:Sound]]

Talk:KDE

Prabuanand — Tue, 14 Apr 2026 05:31:37 GMT

replied and moved the talk page comment about polkit by CCNMXNS

@@ Line 1: / Line 1: @@
 ==Note on reversion of edit id 26401==
 Romw314, I reverted your edit because apk template does not allow a display string different from the package being linked to, the apk command as written int the article {{ic|# apk add plasma}} is correct; the actual package name though is {{pkg|plasma-desktop-meta|arch=}}. It might be possible to change the command to the latter in order to have the display string and the package name match though... Will look into it shortly.
@@ Line 23: / Line 15: @@
 :Dear [[User:Encode|Encode]], I don't use KDE. If based on your testing with a fresh installation, you find this no longer the case, please remove it. -[[User:Prabuanand|Prabuanand]] ([[User talk:Prabuanand|talk]]) 04:44, 28 November 2025 (UTC)
 ::Excellent observations by [[User:Encode|Encode]] and [[User:Prabuanand|Prabuanand]].  Removed '''xf86-input-libinput''' as a Wayland prerequisite and offered a new ''Troubleshooting'' subheading addressing the reported [[KDE#Inputs_not_Working|Inputs not Working]] case, suggesting {{Pkg|libinput-libs}} instead, with an encouragement to report/contribute if the case is encountered.  [[User:John3-16|John3-16]] ([[User talk:John3-16|talk]]) 06:21, 15 December 2025 (UTC)

KDE

Prabuanand — Tue, 14 Apr 2026 05:29:15 GMT

added polkit reference based on Talk page

← Older revision		Revision as of 05:29, 14 April 2026
Line 8:		Line 8:

	{{:Include:Desktop prerequisites}}		{{:Include:Desktop prerequisites}}
	* Enable [[Elogind]] service		* Enable [[Elogind]] service with [[Polkit#Using_polkit_with_elogind\|polkit]].
	* If you need Xwayland and [[Xorg]], run [[Alpine_setup_scripts#setup-xorg-base\|setup-xorg-base]].		* If you need Xwayland and [[Xorg]], run [[Alpine_setup_scripts#setup-xorg-base\|setup-xorg-base]].

Configure Networking

Prabuanand — Tue, 14 Apr 2026 04:16:14 GMT

removed iwd as it is only meant for wireless and not equivalent to NetworkManager

← Older revision		Revision as of 04:16, 14 April 2026
Line 1:		Line 1:
	This page documents the steps to configure the network in Alpine Linux using either [[#Network setup-scripts\|network setup-scripts]] or manually and to [[#Connectivity testing\|test your Internet access]]. Alpine Linux uses [[ifupdown-ng]] for managing its network configuration by default. For additional functionality and graphical or terminal UIs, [[NetworkManager~~]] or [[iwd~~]] can be used.		This page documents the steps to configure the network in Alpine Linux using either [[#Network setup-scripts\|network setup-scripts]] or manually and to [[#Connectivity testing\|test your Internet access]]. Alpine Linux uses [[ifupdown-ng]] for managing its network configuration by default. For additional functionality and graphical or terminal UIs, [[NetworkManager]] can be used.

	For wireless capability, [[Wi-Fi\|wpa_supplicant]] and [[iwd]] are both available and fully supported in Alpine Linux.		For wireless capability, [[Wi-Fi\|wpa_supplicant]] and [[iwd]] are both available and fully supported in Alpine Linux.

Filesystems

Prabuanand — Tue, 14 Apr 2026 03:03:11 GMT

restored Filesystem tools and moved zfs to the table content added for xfs

← Older revision		Revision as of 03:03, 14 April 2026
Line 30:		Line 30:
	\|{{Pkg\|squashfs-tools}} \|\|[[SquashFS]]\|\|mksquashfs\|\|Compressed read-only file system.		\|{{Pkg\|squashfs-tools}} \|\|[[SquashFS]]\|\|mksquashfs\|\|Compressed read-only file system.
	\|-		\|-
	\|{{Pkg\|xfsprogs}} \|\|XFS\|\|mkfs.xfs\|\|		\|{{Pkg\|xfsprogs}} \|\|XFS\|\|mkfs.xfs\|\| High-performance journaling file system for large storages
			\|-
			\|{{Pkg\|zfs}} \|\|[[ZFS]]\|\|-NA-\|\|Advanced copy-on-write filesystem/volume manager
	\|}</onlyinclude>		\|}</onlyinclude>

	~~Additionally, Alpine has~~ [[~~ZFS~~\|~~excellent support~~]] ~~for [https://en.wikipedia.org/wiki/ZFS ZFS], a highly robust copy-on-write filesystem / volume manager~~.		== Filesystem tools ==

			Each filesystem require different packages/programs to format the partitioned space and the appropriate packages needs to be installed first. The list of filesystem tools and the associated formatting commands are listed [[#Overview\|above]].

	== Filesystem labels ==		== Filesystem labels ==

User talk:Apropos

Prabuanand — Tue, 14 Apr 2026 02:34:36 GMT

welcome message to Apropos appreciating their quality contributions

New page

Dear [[User:Apropos|Apropos]], a warm welcome on behalf of the community. I hope that your brief stay here gets extended, so that the community can benefit based on your [[Special:Contributions/Apropos|high quality contributions]] to wiki. Thank you for your contributions to the various wiki pages. If and when time permits, do contribute to [[:Category:Wiki|wiki Help]] pages, so that future contributions to Alpine wiki remain consistent in style thus benefiting the community. -[[User:Prabuanand|Prabuanand]] ([[User talk:Prabuanand|talk]]) 02:34, 14 April 2026 (UTC)

User:Christopher

Christopher — Mon, 13 Apr 2026 22:52:28 GMT

User account Christopher was created

User:Juliuco nikel

Juliuco nikel — Mon, 13 Apr 2026 11:01:51 GMT

User account Juliuco nikel was created

User:AndrewMcCasland

AndrewMcCasland — Mon, 13 Apr 2026 08:45:03 GMT

User account AndrewMcCasland was created

User:Alpinelover420

Ikke — Mon, 13 Apr 2026 04:57:05 GMT

Ikke changed group membership for Alpinelover420 from (none) to nonspam_users

User:Alpinelover420

Alpinelover420 — Mon, 13 Apr 2026 02:21:15 GMT

User account Alpinelover420 was created

ZFS

Apropos — Sun, 12 Apr 2026 05:26:38 GMT

fix: replace markdown code syntax with mediawiki syntax

← Older revision		Revision as of 05:26, 12 April 2026
Line 23:		Line 23:
	=== Create the zpool ===		=== Create the zpool ===

	Replace `/dev/sd...` with the name of the disk or partition where you would like to make the zfs filesystem, such as `/dev/nvme0n1` or `/dev/sda1`. If you would like to be prompted for a password at boot rather than using the key as generated above, then replace `-O keylocation=file:///etc/home.key -O keyformat=raw` with `-O keylocation=prompt -O keyformat=passphrase`. The name "homepool" can be anything.{{Cmd\|<nowiki># zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 \		Replace <code>/dev/sd...</code> with the name of the disk or partition where you would like to make the zfs filesystem, such as <code>/dev/nvme0n1</code> or <code>/dev/sda1</code>. If you would like to be prompted for a password at boot rather than using the key as generated above, then replace <code>-O keylocation=file:///etc/home.key -O keyformat=raw</code> with <code>-O keylocation=prompt -O keyformat=passphrase</code>. The name "homepool" can be anything.{{Cmd\|<nowiki># zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 \
	-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \		-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \
	-O encryption=aes-256-gcm -O keylocation=file:///etc/home.key -O keyformat=raw \		-O encryption=aes-256-gcm -O keylocation=file:///etc/home.key -O keyformat=raw \

← Older revision		Revision as of 16:08, 20 April 2026
Line 116:		Line 116:
	* [[Installing Alpine Linux in a chroot\|Installing Alpine Linux in a chroot]]		* [[Installing Alpine Linux in a chroot\|Installing Alpine Linux in a chroot]]
	* [https://github.com/itoffshore/alpine-linux-scripts setup-partitions]		* [https://github.com/itoffshore/alpine-linux-scripts setup-partitions]
			* [[Data Disk Mode]]
			* [[Diskless Mode]]

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

← Older revision		Revision as of 16:08, 20 April 2026
Line 22:		Line 22:
	* [[QEMU#Live_mode\|QEMU Diskless example]]		* [[QEMU#Live_mode\|QEMU Diskless example]]
	* [[Alpine local backup#Include special files.2Ffolders to the apkovl\|Include special files section]] - To include custom files outside of <code>/etc</code> in .apkovl file.		* [[Alpine local backup#Include special files.2Ffolders to the apkovl\|Include special files section]] - To include custom files outside of <code>/etc</code> in .apkovl file.
			* [[System Disk Mode]]

	[[Category:Diskless]]		[[Category:Diskless]]

← Older revision		Revision as of 03:59, 19 April 2026
Line 1:		Line 1:
	[https://openzfs.org/wiki/Main_Page ZFS] or OpenZFS is an open-source storage platform. It includes the functionality of both traditional file systems and volume manager.		[https://openzfs.org/wiki/Main_Page ZFS] or OpenZFS is an open-source storage platform. It includes the functionality of both traditional file systems and volume manager.

	This page has instructions for creating and ~~auto-mounting~~ an encrypted ZFS drive or partition on an existing encrypted ~~alpine linux~~ system, using ZFS's own encryption capabilities. To do fresh install of Alpine Linux with root partition on ZFS, see [[Root on ZFS with native encryption]].		This page has instructions for creating and automounting an encrypted ZFS drive or partition on an existing encrypted Alpine Linux system using ZFS's own encryption capabilities. To do a fresh install of Alpine Linux with root partition on ZFS, see [[Root on ZFS with native encryption]].

	== Installation ==		== Installation ==
Line 16:		Line 16:
	=== Create an encryption key ===		=== Create an encryption key ===

	This section can be skipped if you intend to unlock the drive by typing a password rather than unlocking automatically. You should use a password instead if your root partition is not encrypted. The location of the file {{Path\|/etc/home.key}} can be ~~anything~~. {{Cmd\|<nowiki># dd if=/dev/random of=/etc/home.key bs=32 count=1		This section can be skipped if you intend to unlock the drive by typing a password rather than unlocking automatically. You should use a password instead if your root partition is not encrypted. The location of the file {{Path\|/etc/home.key}} can be anywhere. {{Cmd\|<nowiki># dd if=/dev/random of=/etc/home.key bs=32 count=1
	# chmod 600 /etc/home.key</nowiki>}}		# chmod 600 /etc/home.key</nowiki>}}

	IMPORTANT: Make sure you don't lose this key by overwriting your root filesystem or ~~anything like that~~. You might want to store a copy of it on an encrypted USB drive, for instance.		IMPORTANT: Make sure you don't lose this key by overwriting your root filesystem or similar. You might want to store a copy of it on an encrypted USB drive, for instance.

	=== Create the zpool ===		=== Create the zpool ===

	Replace <code>/dev/sd...</code> with the name of the disk or partition where you would like to make the zfs filesystem, such as <code>/dev/nvme0n1</code> or <code>/dev/sda1</code>. If you would like to be prompted for a password at boot rather than using the key as generated above, then replace <code>-O keylocation=file:///etc/home.key -O keyformat=raw</code> with <code>-O keylocation=prompt -O keyformat=passphrase</code>. The name "homepool" can be anything.{{Cmd\|<nowiki># zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 \		Replace <code>/dev/sd...</code> with the name of the disk or partition where you would like to make the zfs filesystem, such as <code>/dev/nvme0n1</code> or <code>/dev/sda1</code>. If you would like to be prompted for a password at boot rather than using the key as generated above, then replace <code>-O keylocation=file:///etc/home.key -O keyformat=raw</code> with <code>-O keylocation=prompt -O keyformat=passphrase</code>. The name <var>"homepool"</var> can be anything.{{Cmd\|<nowiki># zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 \
	-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \		-O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \
	-O encryption=aes-256-gcm -O keylocation=file:///etc/home.key -O keyformat=raw \		-O encryption=aes-256-gcm -O keylocation=file:///etc/home.key -O keyformat=raw \
	-O mountpoint=none homepool /dev/sd...</nowiki>}}		-O mountpoint=none homepool /dev/sd...</nowiki>}}

	After completing this, verifying that the pool has been created should return something ~~like:~~:{{Cmd\|<nowiki># zpool status		After completing this, verifying that the pool has been created should return something similar to the following: {{Cmd\|<nowiki># zpool status
	pool: homepool		pool: homepool
	state: ONLINE		state: ONLINE
Line 39:		Line 39:
	errors: No known data errors</nowiki>}}		errors: No known data errors</nowiki>}}

	To create and mount the filesystem issue the command {{Cmd\|<nowiki># zfs create -o mountpoint=/home/username homepool/username		To create and mount the filesystem, issue the command {{Cmd\|<nowiki># zfs create -o mountpoint=/home/username homepool/username
	# chown username:username /home/username </nowiki>}}		# chown username:username /home/username </nowiki>}}

Line 46:		Line 46:
	=== Service configuration ===		=== Service configuration ===

	Setup the following services to ~~auto-mount~~ the new filesystem using [[OpenRC]]		Setup the following services to automount the new filesystem using [[OpenRC]].
	To import existing zpools:{{Cmd\|# rc-update add zfs-import}}		To import existing zpools:{{Cmd\|# rc-update add zfs-import}}
	To load the encryption keys:{{Cmd\|# rc-update add zfs-load-key}}		To load the encryption keys:{{Cmd\|# rc-update add zfs-load-key}}
	Finally to mount the filesystems:{{Cmd\|# rc-update add zfs-mount}}		Finally, to mount the filesystems:{{Cmd\|# rc-update add zfs-mount}}

	Reboot the system, so that the encrypted ZFS drive is automounted and becomes available for use.		Reboot the system so that the encrypted ZFS drive is automounted and becomes available for use.

	== Maintenance ==		== Maintenance ==

	On ~~alpine~~ Linux, there in no cron/script provided to scrub (and eventually trim) your pool(s) on a regular basis, like in other Linux distributions.		On Alpine Linux, there in no cron/script provided to scrub (and eventually trim) your pool(s) on a regular basis, like in other Linux distributions.

	=== Scrub ===		=== Scrub ===

	Scrubbing (and eventually trim) your pool(s) on a [https://blogs.oracle.com/oracle-systems/post/disk-scrub-why-and-when Oracle ~~regular basis~~] ~~is essential~~. The scrub examines all data in the specified pools to verify that it checksums correctly. For replicated (mirror, raidz, or draid) devices, ZFS automatically repairs any damage discovered during the scrub		Scrubbing (and eventually trim) your pool(s) on a regular basis is essential, as discussed in [https://blogs.oracle.com/oracle-systems/post/disk-scrub-why-and-when an official Oracle blog post] on Exadata disk scrubbing. The scrub examines all data in the specified pools to verify that it checksums correctly. For replicated (mirror, raidz, or draid) devices, ZFS automatically repairs any damage discovered during the scrub.

	When scrubbing a pool with encrypted filesystems the keys do not need to be loaded. However, if the keys are not loaded and an unrepairable checksum error is detected the file name cannot be included in the zpool status -v verbose error report.		When scrubbing a pool with encrypted filesystems, the keys do not need to be loaded. However, if the keys are not loaded and an unrepairable checksum error is detected the file name cannot be included in the zpool status -v verbose error report.

	A scrub is split into two parts: metadata scanning and block scrubbing. The metadata scanning sorts blocks into large sequential ranges which can then be read much more efficiently from disk when issuing the scrub I/O.		A scrub is split into two parts: metadata scanning and block scrubbing. The metadata scanning sorts blocks into large sequential ranges which can then be read much more efficiently from disk when issuing the scrub I/O.

	This script is taken from debian zfs scripts. It is used to list the pools, make sure they are online, and no scrub is being done at the time. The contents of the script placed at {{path\|/usr/libexec/zfs/scrub}} is as follows:{{cat\|/usr/libexec/zfs/scrub\|<nowiki>#!/bin/sh -eu		This script is taken from debian zfs scripts. It is used to list the pools, make sure they are online, and no scrub is being done at the time. The contents of the script placed at {{path\|/usr/libexec/zfs/scrub}} are as follows:{{cat\|/usr/libexec/zfs/scrub\|<nowiki>#!/bin/sh -eu

	# directly exit successfully when zfs module is not loaded		# directly exit successfully when zfs module is not loaded
Line 114:		Line 114:
	Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/scrub}}		Make the script executable: {{cmd\|# chmod +x /usr/libexec/zfs/scrub}}

	It is recommended to scrub regularly to assure your pool(s) and datas are in good shape. So the scrub script will be launched once a month, on the 2nd ~~sunday~~ of the month using [[cron]]		It is recommended to scrub regularly to assure your pool(s) and datas are in good shape. In our example, the scrub script will be launched once a month, on the 2nd Sunday of the month using [[cron]].

	Edit your crontabs using the command: {{cmd\|# crontab -e}}		Edit your crontabs using the command: {{cmd\|# crontab -e}}

	and add these 2 lines		and add these 2 lines:
	<pre>		<pre>
	# zfs scrub the ~~second sunday~~ of every month		# zfs scrub the 2nd Sunday of every month
	24 0 8-14 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/scrub ]; then /usr/libexec/zfs/scrub; fi		24 0 8-14 * * if [ $(date +\%w) -eq 0 ] && [ -x /usr/libexec/zfs/scrub ]; then /usr/libexec/zfs/scrub; fi
	</pre>		</pre>