Alpine Linux - User contributions [en]

Podman

2026-05-05T14:32:54Z

Ingrate one:

[https://podman.io/ Podman] is a utility provided as part of the libpod library. It can be used to create and maintain containers. Podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool. In Alpine linux, [[Distrobox]] automatically installs and uses Podman.

== Installation ==

Podman can be installed via {{Pkg|podman}} package in the community repository: {{Cmd|# apk add podman}}

== Configuration ==

To run podman with full functionality you'll need to enable the [[OpenRC#cgroups|cgroups]] service in v2 or '''unified''' mode, which is the current default. {{Cmd|<nowiki># rc-update add cgroups
# rc-service cgroups start</nowiki>}}

The default storage driver setting in {{Path|/etc/containers/storage.conf}} is {{ic|overlay}}. If you're running podman inside a container or using [[Btrfs]] filesystem, change the storage driver to {{ic|vfs}} or {{ic|btrfs}} respectively.

You might need to restart your machine at this stage for the above changes to work properly.

=== Running as root ===

No further steps are required to run as root. Run an example container to verify everything works: {{Cmd|# podman run --rm hello-world}}

=== Running in rootless mode ===

To avoid [[#Permission problems with rootless podman|permission problems]] with rootless podman, consider using [[runc#Crun|Crun]].

To run podman in rootless mode, run the following commands. Replace <USER> with your username in the following commands: {{Cmd|<nowiki># modprobe tun
# echo tun >>/etc/modules
# echo <USER>:100000:65536 >/etc/subuid
# echo <USER>:100000:65536 >/etc/subgid </nowiki>}}

Run an example container to verify everything works: {{Cmd|$ podman run --rm hello-world}}

=== Getting socket ===

To use the podman API or use podman remotely, you need podman socket. Socket is not needed, if podman CLI is used locally.
To get socket, start the podman service: {{Cmd|# rc-service podman start}}
The default location of the socket is {{Path|/run/podman/podman.sock}}

=== Shared mount ===

Containers on linux might require filesystems to be mounted with different propagation than the kernel default of 'private'.
{{Cmd|$ findmnt -o PROPAGATION /}} will produce the following output:
PROPAGATION
private

This section explains few ways to mount your root('''/''') as shared for Distrobox to function. This is not needed when running in rootless mode.

Method1:
Fill in the file {{path|/etc/local.d/mount-rshared.start}} as follows:{{Cat|/etc/local.d/mount-rshared.start|<nowiki>#!/bin/sh
mount --make-rshared /</nowiki>}}

Mark it as executable: {{cmd|# chmod +x /etc/local.d/mount-rshared.start}}

Then enable the service to autostart through [[OpenRC]]. {{cmd|<nowiki># rc-update add local default
# rc-service local start </nowiki>}}

Method2:
An alternate solution with OpenRC v0.54.2-r1 onwards, edit the file {{path|/etc/fstab}} and add {{ic|shared}} option to the root partition such that:{{Cat|/etc/fstab|...
/dev/sda2 / ext4 rw,relatime,shared 0 1
...}}

For both the above cases, after a reboot test the working of shared '''/''' mount using the command: {{Cmd|# findmnt -o PROPAGATION /}} which will produce the following output:
PROPAGATION
shared

=== Docker compose ===

The {{Pkg|podman-compose}} package from provides a drop-in replacement for docker compose. Each time a docker compose is used, a warning will remind that this is using podman under the hood. This warning can be squelched permanently by running: {{cmd|# touch /etc/containers/nodocker}}

== Troubleshooting ==

=== "/" is not a shared mount ===

If you see a warning:
: WARN[0000] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers

You might want to fix this temporarily, for currently running system by issuing the command:{{ic|# mount --make-rshared /}}
Alternately, refer to [[#Shared mount|Shared mount]] section for permanent solution(s).

=== Permission problems with rootless podman ===

You may encounter an error when entering your rootless container:

<code>Error: unable to start container "XYZ": runc: runc create failed: unable to start container process: unable to apply cgroup configuration: rootless needs no limits + no cgrouppath when no permission is granted for cgroups: mkdir /sys/fs/cgroup/XYZ: permission denied: OCI permission denied</code>

This problem may be solved by replacing [[runc|runc]] by [[runc#Crun|Crun]] and recreating your container. Keep in mind that {{Pkg|crun}} replaces {{Pkg|runc}}, which will render containers made with the latter unusable until recreated.

=== Error: netavark: iptables: No such file or directory (os error 2) ===

Podman depends on {{Pkg|iptables}} package:
{{cmd|# apk add iptables}}

== See also ==

* [https://docs.podman.io/en/latest/ Official Podman Documentation]

[[Category:Virtualization]]

Nut-ups

2026-04-17T08:25:39Z

Ingrate one: 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.

This wiki page shows how to install and configure the Network UPS Tools (NUT) package to monitor and report the statistics for a USB-attached Uninterruptible Power Supply (UPS) and make the UPS status available over the network, so that it can be monitored and used to trigger actions in a home automation system like [https://www.home-assistant.io/ Home Assistant].

The UPS model used in the examples is an APC SmartUPS 1000, but any UPS on the [https://networkupstools.org/stable-hcl.html list of compatible models] should work.

== Determine UPS USB parameters ==

The first step is to plug in the USB cable between your UPS and your Alpine Linux host to see how it appears to the system. Information about the UPS can be seen with the {{ic|dmesg}} command. See the example below.{{Cmd|<nowiki># dmesg
[400269.428612] usb 1-3: new low-speed USB device number 3 using xhci_hcd
[400269.580728] usb 1-3: New USB device found, idVendor=051d, idProduct=0002, bcdDevice= 0.06
[400269.580751] usb 1-3: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[400269.580759] usb 1-3: Product: Smart-UPS 1000 FW:600.3.D USB FW:1.4
[400269.580765] usb 1-3: Manufacturer: American Power Conversion
[400269.580771] usb 1-3: SerialNumber: AS0123456789
[400269.687883] usbcore: registered new interface driver usbhid
[400269.687894] usbhid: USB HID core driver
[400269.698356] hid-generic 0003:051D:0002.0001: hiddev96,hidraw0: USB HID v1.10 Device [American Power Conversion Smart-UPS 1000 FW:600.3.D USB FW:1.4] on usb-0000:00:15.0-3/input0</nowiki>}}

From this output, we can see a Smart-UPS 1000 has been detected. We can also see two important parameters: '''idVendor=051d''' and '''idProduct=0002'''. These will be used later in the udev rules, so keep them handy.

These parameters can also simply be retrieved from {{ic|lsusb}}. See the example below.{{Cmd|<nowiki># lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.67-0-rpi dwc_otg_hcd DWC OTG Controller
Bus 001 Device 003: ID 0424:2514
Bus 001 Device 002: ID 0424:2514
Bus 001 Device 004: ID 0463:ffff EATON Ellipse ECO
Bus 001 Device 005: ID 0424:7800</nowiki>}}

From this output, we can see a EATON Ellipse ECO UPS has been detected. We can also see the two important parameters from the ID field, with '''0463''' being the '''idVendor''' and '''ffff''' being the '''idProduct'''.

== Installation ==

Install the {{pkg|nut}} package:{{Cmd|# apk add nut}}

== Configuration ==

All of the configuration files delivered with the package will be in the {{Path|/etc/nut}} subdirectory.

The following commands rename three original configuration files. {{Cmd|<nowiki># mv /etc/nut/nut.conf /etc/nut/nut.bak
# mv /etc/nut/ups.conf /etc/nut/ups.bak
# mv /etc/nut/upsd.conf /etc/nut/upsd.bak</nowiki>}}

Proceed to create the three files with only the configuration parameters needed for our example USB-attached APC Smart-UPS.

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>}}

For remote clients, content as follows: {{Cat|/etc/nut/nut.conf|<nowiki>MODE=netclient</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
port = auto</nowiki>}}

To tell NUT to make the UPS info available on all network interfaces instead of the default i.e localhost only, which is not very useful, create the {{Path|/etc/nut/upsd.conf}} file with content as follows: {{Cat|/etc/nut/upsd.conf|<nowiki>LISTEN 0.0.0.0 3493</nowiki>}}

{{Tip| Replace 0.0.0.0 with the network address of a specific interface if none of the interfaces are appropriate for your situation.}}

Setup all accounts includes an administrator server account with other administration privileges includes to send fsd (forced shutdown) command to all clients with limited account. Create the {{Path|/etc/nut/upsd.users}} file to store all users (Each user are define in square brackets) include a primary/administrator user and secondary/client user to monitor and receive status from the server: {{Cat|/etc/nut/upsd.users|<nowiki>[admin]
password = kjsdahfglkjhlas456
actions = fsd
upsmon primary
[monuser]
password = oiqwegth43
upsmon secondary</nowiki>}}
Read [https://networkupstools.org/docs/man/upsd.users.html UPSD.USERS(5)] for powerful settings to alter connected ups.

The file {{Path|/etc/nut/upsmon.conf}} provide logging, send notifications and store selected users to send or receive commands to ups server. Setup this file on the server MONITOR field with the matched user and ups as follows: {{Cat|/etc/nut/upsd.conf|<nowiki>MONITOR SmartUPS_1000@localhost 1 admin kjsdahfglkjhlas456 primary

NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG LOWBATT "UPS %s battery is low"
NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK "Communications with UPS %s established"
NOTIFYMSG COMMBAD "Communications with UPS %s lost"
NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding"
NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced"
NOTIFYMSG NOCOMM "UPS %s is unavailable"
NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible"

NOTIFYFLAG ONLINE SYSLOG
NOTIFYFLAG ONBATT SYSLOG
NOTIFYFLAG LOWBATT SYSLOG
NOTIFYFLAG FSD SYSLOG
NOTIFYFLAG COMMOK SYSLOG
NOTIFYFLAG COMMBAD SYSLOG
NOTIFYFLAG SHUTDOWN SYSLOG
NOTIFYFLAG REPLBATT SYSLOG
NOTIFYFLAG NOCOMM SYSLOG
NOTIFYFLAG NOPARENT SYSLOG

RBWARNTIME 21600
POWERDOWNFLAG /run/killpower
RUN_AS_USER nut
SHUTDOWNCMD "/sbin/poweroff"</nowiki>}}

Client's upsmon.conf file contains the following: {{Cat|/etc/nut/upsd.conf|<nowiki>MONITOR SmartUPS_1000@(enter the server ip address or hostname) 1 monuser oiqwegth43 secondary
...</nowiki>}}

Read [https://networkupstools.org/docs/man/upsmon.conf.html UPSMON.CONF(5)] to further understand additional features.

=== Configure udev rules ===

To avoid [[#Insufficient permissions on everything|permission errors]], configure '''udev''' for giving NUT access to the USB-attached Smart-UPS 1000. Create the file {{Path|/etc/udev/rules.d/62-nut-usbups.rules}} as follows:{{Cat|/etc/udev/rules.d/62-nut-usbups.rules|<nowiki>SUBSYSTEM=="usb", ATTR{idVendor}=="051d", ATTR{idProduct}=="0002", GROUP="nut"</nowiki>}}
The ''idVendor'' and ''idProduct'' in the first part – i.e ''ATTR{idVendor}=="051d", ATTR{idProduct}=="0002"'' – are unique to your UPS. They were found earlier in the [[#Determine UPS USB parameters| Determining UPS USB parameters]] section. The rest of the line tells '''udev''' what permissions and group ownership to use, and these should be the same regardless of the UPS make and model.

Use the {{ic|udevadm}} command to tell '''udev''' to read in and apply the changes:
{{Cmd|<nowiki># udevadm control --reload
# udevadm trigger</nowiki>}}

{{Tip|Make sure that the {{ic|udev-trigger}} service is added to a runlevel for the udev rule to automatically apply at boot: {{ic|# rc-update add udev-trigger}}.}}
{{Note|There is also a file {{Path|/lib/udev/rules.d/62-nut-usbups.rules}} that has information for all of the UPS models that NUT knows about. You may be able to simply copy this rather than constructing your own rules.}}

== Service configuration ==

The service is called {{ic|nut-upsd}} and can be managed using the standard start|stop|restart commands using standard [[OpenRC]] commands.

{{Tip|Remember to [[#Configure udev rules|configure '''udev''' rules]] and to [[#Testing the configuration|test the configuration]] before proceeding further.}}

Proceed to start the service as follows: {{Cmd|# rc-service nut-upsd start
* /run/nut: creating directory
* /run/nut: correcting owner
Using subdriver: APC HID 0.100
* Starting UPS Server ...}}

Notice that the directory {{Path|/run/nut}} is created automatically the first time.

[[#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}}

Another service {{ic|nut-upsmon}} is needed to read and perform logging monitoring and send force shutdown command to all setup hosts. Follow the instructions about {{ic|nut-upsd}} to enable and start {{ic|nut-upsmon}}

== Live Shutdown Test ==

Input this command {{ic|upsmon -c fsd}} on the server with primary upsmon user to shutdown all hosts includes the server. If any issues need to be Troubleshooting, read [https://networkupstools.org/docs/man/upsmon.conf.html UPSMON.CONF(5)].

== Using NUT ==

Now, the {{ic|upsc}} command can be run against the name added in {{Path|/etc/nut/ups.conf}} to gather all status information about your UPS. Based on the example used on this wiki page:{{Cmd|$ upsc SmartUPS_1000}}
One can also gather specific status information by passing them as an argument: {{Cmd|$ upsc SmartUPS_1000 battery.charge}} This is useful to monitor specific values and/or to initiate actions (e.g. from a script) when specific thresholds are reached.

The [[#See also|See also]] section has documentation links about how to configure NUT to do useful things, such as sending an email, initiating a graceful shutdown when the main power is lost, and how to use Home Assistant to keep tabs on your UPS.

== Troubleshooting ==

=== Testing the configuration ===

Unplug the UPS USB cable from the host, wait a moment, and then reinsert it. Check '''dmesg''' again to make sure that it was detected and that the ''idVendor'' and ''idProduct'' are correct.

Check the permissions on the files in the {{Path|/dev/bus/usb}} subdirectories. One of these represents your UPS. If the '''udev''' rules work correctly, the file should be the one with a group owner of ''nut'' and permissions of 0664. An example is shown below.{{Cmd|# ls -l /dev/bus/usb/001/003
crw-rw-r-- 1 root nut 189, 2 Oct 10 00:53 /dev/bus/usb/001/003}}

Your directory and file names may be different, but at least one of the files should have the group ownership and permissions as shown in the example.

The output from {{ic|dmesg}} should tip you off as to which directory and file it is. Look at the line below from {{ic|dmesg}} and compare the ''usb 1-3'' to the directory entry of the {{Path|/dev/bus/usb/001/003}}file. {{Cat|/dev/bus/usb/001/003|usb 1-3: Manufacturer: American Power Conversion}}

=== Verifying running state ===

A couple of quick commands will ensure that the NUT service is actually running as expected. These are shown in the example below.

alpine:/# rc-service nut-upsd status
* status: started
alpine:/# netstat -tln | grep 3493
tcp 0 0 0.0.0.0:3493 0.0.0.0:* LISTEN

This shows the service running and making the UPS status available on all network interfaces (0.0.0.0) over the default TCP port for NUT (3493).

=== Insufficient permissions on everything ===

<nowiki>
libusb1: Could not open any HID devices: insufficient permissions on everything
No matching HID UPS found
upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
Driver failed to start (exit status=1)</nowiki>

The error message above is due to the USB device having the wrong ownership and permissions. [[#Configure udev rules|Configure '''udev''' rules]] and restart the [[#Service configuration|service]].

== See also ==

* [https://networkupstools.org/ NUT home page]
* [https://networkupstools.org/stable-hcl.html list of NUT compatible models]
* [https://www.home-assistant.io/integrations/nut/ NUT integration for Home Assistant]
* [[Apcupsd]]

[[Category:Monitoring]]
[[Category:System Administration]]
[[Category:Networking]]

Setup Hardware Clock (RTC) Module on a Raspberry Pi

2025-03-12T15:36:01Z

Ingrate one: adding how to for another chipset and add testing hardware bind section.

= Hardware Prerequisites=

Read the documentation on Installing coin battery and mounting it on the correct GPIO pins for your version of Raspberry Pi board.

Example of Raspberry Pi RTC Modules with documentation:
* [https://wiki.dfrobot.com/Raspberry_Pi_RTC_Module_SKU__DFR0386#target_0 DFROBOT - Raspberry Pi RTC Module SKU DFR0386]
* [https://learn.adafruit.com/adding-a-real-time-clock-to-raspberry-pi/wiring-the-rtc Adafruit RTC Modules]
* [http://www.piface.org.uk/assets/piface_clock/PiFaceClockguide.pdf PiFace Real Time Clock]

= Install Software =
Add the modules from the kernel. The documentation should give you required modules paired with chipset mcp7941x, ds1307 or etc.

== /etc/modules|/etc/modules-load.d/i2c.conf ==
Add these modules so they're loaded on boot. You can modprobe each one individually if you don't want to reboot.

'''mcp7941x'''
{{Cat|/etc/modules|i2c_dev
i2c_bcm2708
i2c:mcp7941x
}}

'''ds1307'''
{{Cat|/etc/modules-load.d/i2c.conf|i2c_dev
i2c_bcm2708
rtc-ds1307
}}

== /media/mmcblk0p1/config.txt ==
You will need to mount this as read-write in diskless mode

{{cmd|mount -o remount,rw /media/mmcblk0p1}}

Add these two parameters to the bottom

{{Cat|/media/mmcblk0p1/config.txt|dtparam{{=}}i2c1{{=}}on
dtparam{{=}}i2c_arm{{=}}on
}}

{{cmd|mount -o remount,ro /media/mmcblk0p1}}

Then you will need to reboot.

== Binding the hardware clock device ==

Read the documentation for the mounted RTC module to get an I2C address for hardware binding.
You will want to make sure the device is created when hwclock starts, if it isn't already created. To the bottom of {{Path|/etc/conf.d/hwclock}} add this:

'''mcp7941x'''
{{Cat|/etc/conf.d/hwclock|...
start_pre() {
if [ -d "/sys/class/i2c-adapter/i2c-1/i2c-dev/i2c-1" ]; then
einfo "Creating RTC device";
echo mcp7941x 0x6f > /sys/class/i2c-adapter/i2c-1/new_device
fi
}
}}

For the time being this is necessary but in the future when [https://github.com/raspberrypi/linux/issues/1032 issue 1032] you should be able to just add

{{Cat|/media/mmcblk0p1/config.txt|...
dtparam{{=}}i2c-rtc,mcp7941x
}}

'''ds1307'''
{{Cat|/etc/conf.d/hwclock|...
start_pre() {
einfo "Creating RTC device";
echo ds1307 0x68 > /sys/bus/i2c/devices/i2c-1/new_device
}
}}

In diskless mode save to {{Path|/media/mmcblk0p1/config.txt}}.

In system disk mode save to {{Path|/boot/usercfg.txt}}.

=== Testing hardware bind ===
Before test hardware bind, reboot or run line echo … from {{Path|/etc/conf.d/hwclock}} example
{{cmd|echo ds1307 0x68 > /sys/bus/i2c/devices/i2c-1/new_device }}

Display hardware clock
{{cmd|hwclock }}

Output should display time
<pre> hwclock: Wed Mar 12 17:41:09 2025 0.000000 seconds </pre>
Or error similar below
<pre> hwclock: ioctl 0x80247009 failed: Invalid argument </pre>
meaning hardware bind is successful.

Write system time to RTC module
{{cmd|hwclock -w }}
Run hwclock again to check the time.

== Starting hwclock on boot ==
The hwclock service needs to be started for the hardware clock device to actually do anything. Check if hwclock has been started by running this command:

{{cmd|rc-status {{!}} grep hwclock }}

If it outputs

<pre> hwclock [ started ]</pre>

hwclock has already started. Otherwise start it manually and add it to the default init.d runlevel, so that it starts at boot time:

{{cmd|rc-service hwclock start}}
{{cmd|rc-update add hwclock default}}

If you are running Alpine Linux in the diskless mode (non-persistent root filesystem), save the configuration by:

{{cmd|lbu commit -d}}

[[Category:Hardware]]
[[Category:System Administration]]
[[Category:Raspberry]]

Saving time with Hardware Clock

2025-03-12T12:51:10Z

Ingrate one: Ingrate one moved page Saving time with Hardware Clock to Setup Hardware Clock (RTC) Module on a Raspberry Pi: The title should reflect the purpose of this page for adding an RTC module on a Raspberry Pi.

#REDIRECT [[Setup Hardware Clock (RTC) Module on a Raspberry Pi]]

Setup Hardware Clock (RTC) Module on a Raspberry Pi

2025-03-12T12:51:10Z

= Install Hardware =

I used a [http://www.piface.org.uk/products/piface_clock PiFace Real Time Clock]. After installing the CR1220 battery and correctly mounting on the board, [http://www.piface.org.uk/assets/piface_clock/PiFaceClockguide.pdf see manual] for that.

= Install Software =
Add the modules from the kernel

== /etc/modules ==
Add these modules so they're loaded on boot. You can modprobe each one individually if you don't want to reboot.

{{Cat|/etc/modules|i2c_dev
i2c_bcm2708
i2c:mcp7941x
}}

== /media/mmcblk0p1/config.txt ==
You will need to mount this as read-write

{{cmd|mount -o remount,rw /media/mmcblk0p1}}

Add these two parameters to the bottom

{{Cat|/media/mmcblk0p1/config.txt|dtparam{{=}}i2c1{{=}}on
dtparam{{=}}i2c_arm{{=}}on
}}

{{cmd|mount -o remount,ro /media/mmcblk0p1}}

Then you will need to reboot.

== Binding the hardware clock device ==

You will want to make sure the device is created when hwclock starts, if it isn't already created. To the bottom of {{Path|/etc/conf.d/hwclock}} add this:

{{Cat|/etc/conf.d/hwclock|...
start_pre() {
if [ -d "/sys/class/i2c-adapter/i2c-1/i2c-dev/i2c-1" ]; then
einfo "Creating RTC device";
echo mcp7941x 0x6f > /sys/class/i2c-adapter/i2c-1/new_device
fi
}
}}

For the time being this is necessary but in the future when [https://github.com/raspberrypi/linux/issues/1032 issue 1032] you should be able to just add

{{Cat|/media/mmcblk0p1/config.txt|...
dtparam{{=}}i2c-rtc,mcp7941x
}}

to {{Path|/media/mmcblk0p1/config.txt}}

== Starting hwclock on boot ==
The hwclock service needs to be started for the hardware clock device to actually do anything. Check if hwclock has been started by running this command:

{{cmd|rc-status {{!}} grep hwclock}}

If it outputs

<pre> hwclock [ started ]</pre>

hwclock has already started. Otherwise start it manually and add it to the default init.d runlevel, so that it starts at boot time:

{{cmd|rc-service hwclock start}}
{{cmd|rc-update add hwclock default}}

If you are running Alpine Linux in the diskless mode (non-persistent root filesystem), save the configuration by:

{{cmd|lbu commit -d}}

[[Category:Hardware]]
[[Category:System Administration]]
[[Category:Raspberry]]