Alpine Linux - User contributions [en]

User talk:Bbbhltz

2024-05-01T14:50:46Z

Bbbhltz: Replied to Thomas

Hi,

I would like to add a page to the Wiki and contribute a my five cent.

But I get a spammers not welcome error. How to proceed?

Cheers,

Thomas

: Hi, I would help but I don't have the privilege to add you to a different group. I mean, maybe I can? I saw your message on Mastodon, btw. --[[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 14:50, 1 May 2024 (UTC)

LXQt

2023-09-01T07:58:35Z

Bbbhltz: /* Optional Configuration */ use Path template instead of <code>

{{TOC right}}

[[File:LXQt Minimal Installation.png | thumb | LXQt 1.3.0 Basic Install with Papirus icons]]

'''[https://lxqt-project.org/ LXQt]''' is a lightweight QT based desktop environment, LXQt was originally a port of LXDE to QT (called LXDE-Qt), it was created due to LXDE maintainer Hong Jen Yee being dissatisfied with GTK 3, on 21 July 2013 the LXDE(-Qt) and [https://en.wikipedia.org/wiki/Razor-qt Razor-qt] projects merged creating LXQt.

== Prerequisites ==

* [[Installation|Install]] Alpine Linux
* [[Setting_up_a_new_user#Creating_a_new_user|Create a user account]] (optional but recommended)
* [[Repositories#Enabling_the_community_repository|Enable the Community repository]]
* [[Alpine_setup_scripts#setup-xorg-base|Install Xorg]]

== Basic LXQt Desktop Installation ==

{{Cmd|# apk add {{Pkg|lxqt-desktop}} {{Pkg|lximage-qt}} {{Pkg|obconf-qt}} {{Pkg|pavucontrol-qt}} {{Pkg|screengrab}} \
{{Pkg|arandr}} \
{{Pkg|dbus}} \
{{Pkg|sddm}} \
{{Pkg|sddm-openrc}}}}

{{Note|By default LXQt uses [[Openbox]] as its window manager (it is a dependency of the {{Pkg|lxqt-desktop}} package), but LXQt supports many different window managers, See: [https://github.com/lxqt/lxqt/wiki/ConfigWindowManagers Window Managers Configuration on the LXQt GitHub wiki]}}

Starting dbus (desktop bus) service:
{{Cmd|# rc-service dbus start}}

Enabling dbus to start on boot:
{{Cmd|# rc-update add dbus}}

If dbus is not running it leads to issues like missing icons and keyboard shortcuts.

Enabling udev service:
{{Cmd|# setup-devd udev}}

== Starting LXQt ==

=== With a display manager (DM) ===

If the package {{Pkg|sddm}} has been installed, SDDM may be started to log in graphically with your new user.
{{Cmd|# rc-service sddm start}}

After correct operation is verified, sddm can be enabled to start up during boot:
{{Cmd|# rc-update add sddm}}

=== From the command line ===

LXQt may be started with:
{{cmd|# startlxqt}}

== Localized keyboard layout ==

Preferences → LXQt Settings → Keyboard and Mouse → Keyboard Layout

== Allowing shut down and reboot ==

To enable users to shut down the machine or reboot, the packages {{Pkg|elogind}} and {{Pkg|polkit-elogind}} need to be installed.
{{Cmd|# apk add elogind polkit-elogind}}

A reboot is required to let it take effect.

== Auto-mounting USB drives ==

To enable automatic mounting of USB drives, install these packages:
{{Cmd|# apk add gvfs udisks2}}

Depending on what devices you intend to mount, some additional packages may be needed:
{{Cmd|ntfs-3g Stable, full-featured, read-write NTFS (driver)
gvfs-cdda CDDA support for gvfs
gvfs-afp AFP support for gvfs
gvfs-goa GNOME Online Accounts support for gvfs
gvfs-mtp MTP support for gvfs
gvfs-smb Windows fileshare support for gvfs
gvfs-lang Languages for package gvfs
gvfs-afc Apple mobile devices support for gvfs
gvfs-nfs NFS support for gvfs
gvfs-dev Backends for the gio framework in GLib (development files)
gvfs-archive Archiving support for gvfs
gvfs-dav WebDAV support for gvfs
gvfs-fuse FUSE support for gvfs
gvfs-gphoto2 gphoto2 support for gvfs
gvfs-avahi DNS-SD support for gvfs}}

To list descriptions of all gvfs- packages:

{{cmd|# apk info -d gvfs-*}}

== Network browsing ==

For browsing of network shares within LXQt that works with file associations, you can install the gvfs packages for the network protocols you use.

For example, to browse in a SMB/cifs windows network:

{{Cmd|# apk add gvfs-smb}}

(Check: If the above may already be sufficient for gvfs to initiate the fuse kernel module. Else, try to identify if there are necessary steps in:)

{{Cmd|# apk add gvfs-fuse}}

The OpenRC script for fuse is in a separate package.

{{Cmd|# apk add fuse-openrc}}

Then the fuse service can be started manually.

{{Cmd|# rc-service fuse start}}

If it works, the fuse service can be added to start up automatically at boot time:

{{Cmd|# rc-update add fuse}}

== Enabling privilege escalation GUI ==

To enable the privilege escalation GUI for a doas/sudo user, you need to install {{Pkg|elogind}}, {{Pkg|polkit-elogind}}, and {{Pkg|sddm}}.

To have elogind run, either make them start automatically at system start:

{{Cmd|# rc-update add elogind}}

or start them manually for this time only:

{{Cmd|# rc-service elogind start }}

== Panel Widgets ==

If you cannot add the CPU and System Statistics widgets to the panel, make sure {{Pkg|libstatgrab}} and {{Pkg|libsysstat}} are installed.

== Troubleshooting ==

=== Missing Icons and Fonts ===

By default a Desktop Environments needs icons. {{Pkg|adwaita-icon-theme}} is a good start.
{{Cmd|# apk add adwaita-icon-theme}}

See [[Fonts]] for more information on fonts.

== Optional Configuration ==

=== Screen Compositor ===

To enable different effects (transparency, for example) {{Pkg|picom}} can be used.

After installation, add it to the ''Autostart'' section of the '''LXQt Session Settings'''.

The default configuration is available in {{Path|/etc/xdg/picom.conf.example}}. For modifications, it can be copied to {{Path|~/.config/picom/picom.conf}} or {{Path|~/.config/picom.conf}}.

Either modify the config file to your taste, or change the Autostart command line options. For example, <code>picom --vsync -r 12 --no-fading-openclose -b</code>.

=== Appearance Tweaking ===

==== Location of appearance-related configuration files ====

User-specific configuration is stored in {{Path|~/.config/lxqt/}}.

LXQt themes are [https://doc.qt.io/qt-6/stylesheet.html qss stylesheets]. They are located in {{Path|/usr/share/lxqt/themes/}} or {{Path|~/.local/share/lxqt/themes}}.

Qt Palette colors can be modified in lxqt-config-appearence > Widget Style > Qt Palette. Custom palettes are saved in {{Path|~/.local/share/lxqt/palettes/}}.

==== Additional QT Styles ====

Several packages provide additional QT Styles:

{{Cmd|# apk add {{Pkg|adwaita-qt}} {{Pkg|breeze}} {{Pkg|oxygen}}}}

They also provide additional cursors.

==== Consistant Theming ====

Adding the KEY=VAL <code>QT_QPA_PLATFORMTHEME=lxqt</code> to the Environment section of the Session Settings [https://github.com/lxqt/lxqt-qtplugin#configuration-usage is suggested by the LXQt developers]. Then every Qt5 program can load the theme plugin.

Another option, however, is to to install the package {{Pkg|qt5ct}} (from [[Repositories | Testing]]) and appending the line <code>QT_QPA_PLATFORMTHEME=qt5ct</code> to the environmental settings in the Environment section of the Session Settings will allow you to achieve a unified appearance between apps. Then, in the LXQt Appearance Configuration, under Widget Style, set Qt Style to <code>qt5ct-style</code>.

==== Additional Packages ====

When using themes found around the web, it is possible that they are dependant on different packages. Consider using {{Pkg|qt5-qtgraphicaleffects}}, {{Pkg|qt5-qtquickcontrols}}, and {{Pkg|qt5-qtquickcontrols2}}.

== Documentation ==

* {{Pkg|lxqt-config-doc}}
* {{Pkg|lxqt-openssh-askpass-doc}}
* {{Pkg|lxqt-panel-doc}}
* {{Pkg|lxqt-policykit-doc}}
* {{Pkg|lxqt-runner-doc}}
* {{Pkg|lxqt-session-doc}}
* {{Pkg|lxqt-sudo-doc}}

== Development files ==

* {{Pkg|lxqt-globalkeys-dev}}
* {{Pkg|lxqt-panel-dev}}

== Misc ==

* {{Pkg|lxqt-build-tools}}

== See Also ==

* [[Installation#Post-Install|Post Install]]
* [[Desktop environments and Window managers]]

= External Resources =

* [https://lxqt.github.io/ LXQt Homepage]
* [https://github.com/lxqt/lxqt LXQt on GitHub]
* [https://wiki.archlinux.org/title/LXQt LXQt entry on ArchWiki]
* [https://github.com/sddm/sddm SDDM Project on GitHub]

[[Category:Desktop]]
[[Category:Desktop Environments]]

Kexec

2023-08-13T15:42:23Z

Bbbhltz: Added category, minor formatting and template changes

[https://en.wikipedia.org/wiki/Kexec Kexec] is a system call that enables loading and booting into another kernel. This is useful for fast reboots that skip the BIOS or UEFI initialisation process.

On a typical Alpine setup, it can be used via:

{{Cmd|# kexec -l /boot/vmlinuz-edge --initrd \
/boot/initramfs-edge --reuse-cmdline
# kexec -e}}

{{Warning|Running <code>kexec -e</code> does not unmount any filesystems or gracefully shut down any services!}}

There are no Alpine-specific considerations for Kexec. Please review the man page and existing references below of more details. This page is deliberately kept short in order to avoid duplicating existing documentation.

== See also ==

* [https://wiki.gentoo.org/wiki/Kexec Gentoo Wiki: Kexec]
* [https://wiki.archlinux.org/title/Kexec ArchWiki: Kexec]

[[Category: Booting]]
[[Category: Kernel]]

Flatpak

2023-08-11T11:21:08Z

Bbbhltz: /* Runtime dependencies */ bullets, template use

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snap_(software) Snap],

== Setup / Installation ==

=== Runtime dependencies ===

* {{Pkg|dbus}}
* {{Pkg|xdg-desktop-portal}}
* an implementation of <code>xdg-desktop-portal</code>, e.g. {{Pkg|xdg-desktop-portal-gtk}}

{{Note|If you are running a window manager from {{Path|.xinitrc}}, make sure you are running a <code>dbus</code> session explicitly, i.e.:

{{Cmd|# exec dbus-launch --exit-with-session your_favourite_wm}}}}

=== Installing Flatpak Itself ===

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add {{Pkg|flatpak}}}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|$ flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

== Usage ==

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

=== Search ===

To search for applications run '''flatpak search <appplicationname>'''

Example:

~'''$''' flatpak search chromium

Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub


 

=== Install ===

To install a package run '''flatpak install <applicationname>'''

~'''$''' flatpak install com.github.Eloston.UngoogledChromium

Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:


or if you dont know or dont want to type the exact package name:

~'''$''' flatpak install chromium

Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:


=== Remove ===

To remove a package run: '''flatpak remove <applicationname>'''

~'''$''' flatpak remove com.github.Eloston.UngoogledChromium

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:


or if you dont know or dont want to type the exact package name:

~'''$''' flatpak remove chromium

Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:


== Developers ==

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

== Troubleshooting ==

=== Permission errors ===

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group.

{{Note|You need to log out and log back in or reboot for the group change(s) to take effect}}

=== Fixing audio issues ===

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in {{Path|/etc/profile.d/xdg_runtime_dir.sh}} and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:

{{Cmd|$ pulseaudio --start && flatpak run com.example.Example}}

== Links ==
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

[[Category:Package Manager]]
[[Category: Desktop]]

Flatpak

2023-08-11T11:19:49Z

Bbbhltz: /* Setup / Installation */ formatting, template use

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snap_(software) Snap],

== Setup / Installation ==

=== Runtime dependencies ===

- {{Pkg|dbus}}

- {{Pkg|xdg-desktop-portal}}

- an implementation of <code>xdg-desktop-portal</code>, e.g. {{Pkg|xdg-desktop-portal-gtk}}

Note if you are running a window manager from {{Path|.xinitrc}}, make sure you are running a <code>dbus</code> session explicitly, i.e.:

{{Cmd|# exec dbus-launch --exit-with-session your_favourite_wm}}

=== Installing Flatpak Itself ===

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add {{Pkg|flatpak}}}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|$ flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

== Usage ==

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

=== Search ===

To search for applications run '''flatpak search <appplicationname>'''

Example:

~'''$''' flatpak search chromium

Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub


 

=== Install ===

To install a package run '''flatpak install <applicationname>'''

~'''$''' flatpak install com.github.Eloston.UngoogledChromium

Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:


or if you dont know or dont want to type the exact package name:

~'''$''' flatpak install chromium

Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:


=== Remove ===

To remove a package run: '''flatpak remove <applicationname>'''

~'''$''' flatpak remove com.github.Eloston.UngoogledChromium

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:


or if you dont know or dont want to type the exact package name:

~'''$''' flatpak remove chromium

Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:


== Developers ==

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

== Troubleshooting ==

=== Permission errors ===

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group.

{{Note|You need to log out and log back in or reboot for the group change(s) to take effect}}

=== Fixing audio issues ===

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in {{Path|/etc/profile.d/xdg_runtime_dir.sh}} and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:

{{Cmd|$ pulseaudio --start && flatpak run com.example.Example}}

== Links ==
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

[[Category:Package Manager]]
[[Category: Desktop]]

UniFi Controller

2023-07-04T17:48:35Z

Bbbhltz: Used warning template

{{TOC right}}

{{Warning|The Ubiquiti Unifi controller Linux self-contained Java image relies on MongoDB, and MongoDB has been removed from Alpine Linux after version 3.9 due to SPL license changes, so this guide doesn't work.}}

== Introduction ==

This guide explains how to install the generic Unix UniFi Controller, as available from [http://www.ui.com/ Ubiquiti Networks]. At the time of writing this, a native Alpine Linux package is not available.

Furthermore, this guide uses the incredibly reliable and efficient [http://www.skarnet.org/software/s6/ s6] supervision suite to start and control the UniFi Controller.

A summarized schematic of what will be installed on the filesystem.

The choice of {{path|/srv}} for the UniFi Controller's root directory is based on the fact that it contains both run-time and configuration data, so installing to {{path|/usr/local}}, {{path|/opt}} or {{path|/home}} didn't seem appropriate. Feel free to adjust the steps below, replacing {{path|/srv/unifi}} with wherever you would prefer to install the UniFi Controller software.

<pre>
/
`--etc
|-- unifi
| `-- log
|-- srv
| `-- unifi
| |-- bin
| |-- conf
| |-- data
| |-- dl
| |-- lib
| |-- logs
| |-- run
| `-- webapps
|-- run
| `-- openrc
| `-- s6-scan
| `-- unifi --> /etc/unifi
`-- var
`-- log
`-- unifi
</pre>

= Prerequisite Packages =

== OpenJDK 8 JRE ==

Install <code>openjdk8-jre</code> from the community repository.

Edit <code>/etc/apk/repositories</code> and uncomment the appropriate community repository for your Alpine version:

<code><nowiki>http://host.name/alpine_version/community</nowiki></code>

Update the package cache.

<code>apk update</code>

Install the package.

<code>apk add openjdk8-jre</code>

== MongoDB ==

Install MongoDB

<code>apk add mongodb</code>

== s6 ==

Install [http://www.skarnet.org/software/s6/ s6]

<code>apk add s6</code> which is a service supervision suite, for reliably and efficiently starting, stopping and keeping services running.

The below shows a schematic process tree of how the UniFi Controller will be started and supervised by s6. The controller is written in Java, hence the Java process and it in turn, launches a dedicated instance of MongoDB to store its configuration and run-time data.

<pre>
init
`-- s6-svscan
`-- s6-supervise
|-- s6-log
`-- java
`-- mongod
</pre>

= Install UniFi Controller =

Create the <code>unifi</code> user and group.

<code>adduser -D -H -h /srv/unifi unifi</code>

Change to the parent folder within which you wish to install the UniFi Controller.

<code>cd /srv</code>

Download the generic unix archive of the <code>VERSION</code> you wish to install.

<code>wget http://www.ubnt.com/downloads/unifi/VERSION/UniFi.unix.zip</code>

Unpack the archive.

<code>unzip UniFi.unix.zip</code>

Rename the unpacked directory.

<code>mv UniFi unifi</code>

Change ownership.

<code>chown -R unifi:unifi unifi</code>

Lock down permissions.

<code>chmod o-rwx unifi</code>

Change into the UniFi bin directory.

<code>cd /srv/unifi/bin</code>

Remove the existing file.

<code>rm mongod</code>

Create a symlink to <code>/usr/bin/mongod</code>

<code>ln -s /usr/bin/mongod</code>

= Configure Service Management =

== Create UniFi Service Directory and Files ==

Create an s6 service directory for UniFi.

<code>mkdir -p /etc/unifi/log</code>

Add the <code>run</code> script, using your favourite editor.

<code>vim /etc/unifi/run</code>

Copy and paste the following into it.

<pre>
#!/bin/ash

user='unifi'
group='unifi'

exec 2>&1

base='/srv/unifi'

if [ -d $base ]; then
cd $base
chown -R $user:$group .
version=`head -1 webapps/ROOT/app-unifi/.version`
echo "Starting UniFi Controller $version"
exec s6-setuidgid $user java -jar lib/ace.jar start
else
echo "Missing $base ... aborting"
touch down
fi
</pre>

Ensure that the <code>run</code> script is executable:

<code>chmod 755 /etc/unifi/run</code>

Add the <code>log/run</code> script, using your favourite editor.

<code>vim /etc/unifi/log/run</code>

Copy and paste the following into it.

<pre>
#!/bin/ash

log_user='log'

exec s6-setuidgid $log_user s6-log -b n20 s1000000 t /var/log/unifi
</pre>

Ensure that the log/run script is executable:

<code>chmod 755 /etc/unifi/log/run</code>

== Create log User and Directory ==

Create the <code>log</code> user and group.

<code>adduser -D -H -h /var/log log</code>

Create the <code>/var/log/unifi</code> directory

<code>mkdir -p /var/log/unifi</code>

Update the directory ownership.

<code>chown log:log /var/log/unifi</code>

Lock down the permissions.

<code>chmod 750 /var/log/unifi</code>

== Create the OpenRC Service Script ==

Open the script file using your favourite editor.

<code>vim /etc/init.d/unifi</code>

Paste the following into it.

<pre>
#!/sbin/openrc-run

name="unifi"
supervisor=s6
s6_service_path="${RC_SVCDIR}/s6-scan/${name}"

depend() {
need net s6-svscan
after firewall
}

start_pre() {
if [ ! -L "${RC_SVCDIR}/s6-scan/${name}" ]; then
ln -s "/etc/${name}" "${RC_SVCDIR}/s6-scan/${name}"
fi
}
</pre>

Ensure that the script is executable.

<code>chmod 755 /etc/init.d/unifi</code>

== Start the UniFi Controller Service ==

<code>rc-service unifi start</code>

== Configure the UniFi Controller Service to start on boot ==

<code>rc-update add unifi boot</code>

= Simple Backup Script =

Create <code>/usr/local/bin/unifi-backup</code> using your favourite editor.

'''Note:''' This script assumes the use of s6-svc to control unifi. I will modify it in time, to use rc-service instead.

Paste the following into the file.

<pre>
#!/bin/ash

conf_dir='/etc/unifi'
backup_dir='/srv/backup/unifi'
service_dir='/run/openrc/s6-scan/unifi'

start_state='down'

if s6-svok $service_dir; then
if s6-svstat -o up,ready $service_dir | grep -q true; then
echo 'Stopping the UniFi Controller'
start_state='up'
s6-svc -d $service_dir
sleep 3
fi
else
echo 'Warning: The UniFi Controller is not supervised'
exit 1
fi

if s6-svstat -o up $service_dir | grep -q false; then
echo 'Success: The UniFi Controller was stopped'
else
echo 'Error: The UniFi Controller is still running'
exit 1
fi

stamp=`date +%Y-%m-%d_%H%M%S`

mkdir -p $backup_dir
cd $backup_dir
mkdir "data-$stamp"

echo "Backing up to /srv/backup/unifi/data-$stamp.tar.gz"

if rsync -az /srv/unifi/data/ "data-$stamp"; then
echo '* rsync succeeded'
if tar czf "data-$stamp.tar.gz" "data-$stamp"; then
echo '* tar succeeded'
rm -rf "data-$stamp"
echo 'Backup succeeded'
else
echo 'Backup failed: tar failed'
exit 1
fi
fi

if [ "$start_state" == 'up' ]; then
echo 'Starting the UniFi Controller'
s6-svc -u $service_dir
sleep 5
s6-svstat $service_dir
fi
</pre>

[[category:Networking]]

NZBGet

2023-07-04T17:31:59Z

Bbbhltz: formatting and template use

{{DISPLAYTITLE:NZBGet}}
{{TOC right}}

== Introduction ==

* This guide explains how to install the popular service [https://nzbget.net/ NZBGet] on Alpine Linux. Specifically, the environment used is 3.18 running in an LXC container. This guide should still work in a standard Alpine Linux install.
* This guide sets up NZBGet as a standard rc init service.
* The path {{path|/opt}} is used in this guide, however the choice of path is immaterial to the outcome, for example, {{path|/srv}} should work fine.
* This guide assumes all commands are run as root unless specified.

== Download and install nzbget ==

Fetch and install the latest NZBGet install script. (If you have security concerns, NZBGet code is available to inspect on [https://github.com/nzbget/nzbget GitHub]).

{{Cmd|$ wget https://nzbget.net/download/nzbget-latest-bin-linux.run}}

Run the install script.

{{Cmd|$ chmod +x nzbget-latest-bin-linux.run && ./nzbget-latest-bin-linux.run}}

Move the nzbget directory to {{path|/opt}}}

{{Cmd|# mv nzbget /opt/}}

== Create NZBGet Service ==

Create the NZBGet init file:

{{Cat|/etc/init.d/nzbget|#!/sbin/openrc-run

depend() {
need net
}

start() {
/opt/nzbget/nzbget -D
}

stop() {
/opt/nzbget/nzbget -Q
}
}}

Notice that the commands <code>/opt/nzbget/nzbget -D</code> and <code>/opt/nzbget/nzbget -Q</code> are used to cleanly start and stop the service.

Add the service to rc init:

{{Cmd|# rc-update add nzbget}}

Start the service:

{{Cmd|# rc-service nzb start}}

== Notes ==

* At this point, you should be able to reach nzbget at '''http://<YOURIP>:6789'''. You should be able to start and stop the nzbget service and the service should start after a system restart/reboot:

{{Cmd|# rc-service nzb start}}

{{Cmd|# rc-service nzb stop}}

* Any further configs can be set using the webgui or in {{path|/opt/nzbget/nzbget.conf}}.
* Of note is the line in {{path|/opt/nzbget/nzbget.conf}}:

<code>DaemonUsername=root</code>

This allows the service to start and run as a specific user, which is a common setup if NZBGet is used in conjunction with other media managers and shared storage. Note that any working directories specified in the settings will require their permissions updated to work correctly.
* NZBGet is quite descriptive in its logs. Check NZBGet's '''Messages''' section for errors, including permissions and paths.

== Updating NZBGet ==

As of version 21.2, the certificate that ships with NZBGet for updating from nzbget.net is expired and updates will consequently fail until it is updated. Fortunately, this can be rectified:

Stop the nzbget service:

{{Cmd|# rc-service nzbget stop}}

If you run the nzbget service under any other user than root, change this back to root temporarily for the update in {{path|/opt/nzbget/nzbget.conf}}:

<code>DaemonUsername=root</code>

Fetch the new and valid certificate:

{{Cmd|$ curl --remote-name --time-cond cacert.pem https://nzbget.net/info/cacert.pem}}

Move the new certificate to the correct path:

{{Cmd|# mv cacert.pem /opt/nzbget/cacert.pem}}

Start the NZBGet service:

{{Cmd|# rc-service nzbget start}}

Navigate to your instance of NZBGet, Settings, System, Update NZBGet:

[[File:2023-07-04 01-07.png|thumb|right|100px|nzbget update screenshot]]

If required, stop the nzbget service again and revert the <code>DaemonUsername</code> to its normal value in {{path|/opt/nzbget/nzbget.conf}}.

[[category:Networking]]

Iwd

2023-07-03T09:44:42Z

Bbbhltz: /* Usage (iwctl) */ notes on diskless and ipv6

{{DISPLAYTITLE:iwd}}

iwd ('''i'''Net '''W'''ireless '''D'''aemon) is a wireless daemon for Linux. It is written by Intel and aims to replace <code>wpa_supplicant</code>. The core goal of the project is to optimize resource utilization: storage, runtime memory and link-time costs. This is accomplished by not depending on any external libraries and utilizes features provided by the Linux Kernel to the maximum extent possible. The result is a self-contained environment that only depends on the Linux Kernel and the runtime C library.

Potential benefits of iwd include:

* simplification of network management
* faster network discovery
* fast and reliable roaming
* using less system resources
* using features offered by the Linux kernel
* support for enterprise security methods like EAP
* support for kernel asymmetric key rings and [https://en.wikipedia.org/wiki/Trusted_Platform_Module Trusted Platform Modules (TPM)]
* support for multiple clients

== Installation ==

Install <code>iwd</code>:

{{Cmd|# apk add {{Pkg|iwd}}}}

== Usage (iwctl) ==

The iwd package provides the client program <code>iwctl</code>, the daemon <code>iwd</code> and the Wi-Fi monitoring tool <code>iwmon</code>.

Begin by starting the client:

{{Cmd|$ iwctl}}

To list all available commands:

[iwd]# help

=== Connect to a network ===

First, if you do not know your wireless device name, list all Wi-Fi devices:

[iwd]# device list

If the device or its corresponding adapter is turned off, turn it on:

[iwd]# device ''device'' set-property Powered on

[iwd]# adapter ''adapter'' set-property Powered on

Then, to initiate a scan for networks (note that this command will not output anything):

[iwd]# station ''device'' scan

You can then list all available networks:

[iwd]# station ''device'' get-networks

Finally, to connect to a network:

[iwd]# station ''device'' connect ''SSID''

If a passphrase is required, you will be prompted to enter it. Alternatively, you can supply it as a command line argument:

{{Cmd|$ iwctl –passphrase ''passphrase'' station ''device'' connect ''SSID''}}

{{Note|
* iwd automatically stores network passphrases in the {{Path|/var/lib/iwd}} directory and uses them to auto-connect in the future.
* If you run diskless Alpine, be sure to commit: {{Cmd|# lbu add /var/lib/iwd && lbu commit -d}}
* To connect to a network with spaces in the SSID, the network name should be double quoted when connecting.
* iwd only supports PSK pass-phrases from 8 to 63 ASCII-encoded characters. }}

==== IPV6 ====

iwd supports IPv6, but it is disabled by default. To enable it, add the following to the configuration file:

{{Cat|/etc/iwd/main.conf|<nowiki>#[Network]
EnableIPv6=true</nowiki>}}

=== Disconnect from a network ===

To disconnect from a network:

[iwd]# station ''device'' disconnect

=== Show device and connection information ===

To display the details of a WiFi device, like MAC address:

[iwd]# device ''device'' show

To display the connection state, including the connected network of a Wi-Fi device:

[iwd]# station ''device'' show

=== Manage known networks ===

To list networks you have connected to previously:

[iwd]# known-networks list

To forget a known network:

[iwd]# known-networks ''SSID'' forget

{{Note|It is not possible to assign a priority to a network, instead iwd will prioritize networks based on:

* signal strength level
* security features
* maximum rate
* channel utilization
* time since the last connect.}}

== Dedicated GUI (iwgtk) ==

[[File:Iwgtk screenshot.png|thumb|right|100px|alt=iwgtk showing list of networks|iwgtk]]

iwgtk is a wireless networking GUI for Linux with supported functionality similar to that of <code>iwctl</code>. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.

{{Cmd|# apk add {{Pkg|iwgtk}}}}

== Usage as a Backend ==

iwd can be used as a replacement backend for NetworkManager. See [[NetworkManager#iwd_backend|the relevant NetworkManager section]] for more information.

== See also ==

* [[Wi-Fi]]
* [https://wiki.gentoo.org/wiki/Iwd iwd on Gentoo Wiki]
* [https://wiki.archlinux.org/title/Iwd iwd on ArchWiki]
* [https://iwd.wiki.kernel.org/start iwd Wiki]
* [https://github.com/J-Lentz/iwgtk iwgtk: Lightweight wireless networking GUI (front-end for iwd)]

[[Category:Networking]]

Iwd

2023-07-03T09:35:48Z

Bbbhltz: added link to Wi-Fi entry

{{DISPLAYTITLE:iwd}}

iwd ('''i'''Net '''W'''ireless '''D'''aemon) is a wireless daemon for Linux. It is written by Intel and aims to replace <code>wpa_supplicant</code>. The core goal of the project is to optimize resource utilization: storage, runtime memory and link-time costs. This is accomplished by not depending on any external libraries and utilizes features provided by the Linux Kernel to the maximum extent possible. The result is a self-contained environment that only depends on the Linux Kernel and the runtime C library.

Potential benefits of iwd include:

* simplification of network management
* faster network discovery
* fast and reliable roaming
* using less system resources
* using features offered by the Linux kernel
* support for enterprise security methods like EAP
* support for kernel asymmetric key rings and [https://en.wikipedia.org/wiki/Trusted_Platform_Module Trusted Platform Modules (TPM)]
* support for multiple clients

== Installation ==

Install <code>iwd</code>:

{{Cmd|# apk add {{Pkg|iwd}}}}

== Usage (iwctl) ==

The iwd package provides the client program <code>iwctl</code>, the daemon <code>iwd</code> and the Wi-Fi monitoring tool <code>iwmon</code>.

Begin by starting the client:

{{Cmd|$ iwctl}}

To list all available commands:

[iwd]# help

=== Connect to a network ===

First, if you do not know your wireless device name, list all Wi-Fi devices:

[iwd]# device list

If the device or its corresponding adapter is turned off, turn it on:

[iwd]# device ''device'' set-property Powered on

[iwd]# adapter ''adapter'' set-property Powered on

Then, to initiate a scan for networks (note that this command will not output anything):

[iwd]# station ''device'' scan

You can then list all available networks:

[iwd]# station ''device'' get-networks

Finally, to connect to a network:

[iwd]# station ''device'' connect ''SSID''

If a passphrase is required, you will be prompted to enter it. Alternatively, you can supply it as a command line argument:

{{Cmd|$ iwctl –passphrase ''passphrase'' station ''device'' connect ''SSID''}}

{{Note|
* iwd automatically stores network passphrases in the {{Path|/var/lib/iwd}} directory and uses them to auto-connect in the future.
* To connect to a network with spaces in the SSID, the network name should be double quoted when connecting.
* iwd only supports PSK pass-phrases from 8 to 63 ASCII-encoded characters. }}

=== Disconnect from a network ===

To disconnect from a network:

[iwd]# station ''device'' disconnect

=== Show device and connection information ===

To display the details of a WiFi device, like MAC address:

[iwd]# device ''device'' show

To display the connection state, including the connected network of a Wi-Fi device:

[iwd]# station ''device'' show

=== Manage known networks ===

To list networks you have connected to previously:

[iwd]# known-networks list

To forget a known network:

[iwd]# known-networks ''SSID'' forget

{{Note|It is not possible to assign a priority to a network, instead iwd will prioritize networks based on:

* signal strength level
* security features
* maximum rate
* channel utilization
* time since the last connect.}}

== Dedicated GUI (iwgtk) ==

[[File:Iwgtk screenshot.png|thumb|right|100px|alt=iwgtk showing list of networks|iwgtk]]

iwgtk is a wireless networking GUI for Linux with supported functionality similar to that of <code>iwctl</code>. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.

{{Cmd|# apk add {{Pkg|iwgtk}}}}

== Usage as a Backend ==

iwd can be used as a replacement backend for NetworkManager. See [[NetworkManager#iwd_backend|the relevant NetworkManager section]] for more information.

== See also ==

* [[Wi-Fi]]
* [https://wiki.gentoo.org/wiki/Iwd iwd on Gentoo Wiki]
* [https://wiki.archlinux.org/title/Iwd iwd on ArchWiki]
* [https://iwd.wiki.kernel.org/start iwd Wiki]
* [https://github.com/J-Lentz/iwgtk iwgtk: Lightweight wireless networking GUI (front-end for iwd)]

[[Category:Networking]]

Wi-Fi

2023-07-03T09:35:13Z

Bbbhltz: formatting, templates

This page describes how to set up a wireless network connection with WPA encryption.

Choose a wireless daemon between {{Pkg|iwd}} and {{Pkg|wpa_supplicant}}

== Prerequisites ==

Working wireless drivers
{{Note|in most cases installing {{Pkg|linux-firmware}} should get you the required drivers. Installation of this package can produce errors on diskless or data disk modes. If such errors occur, switch to system disk mode.}}

If you are using a '''Broadcom chipset''', see the [[#Broadcom_Wi-Fi_Chipset_Users|Broadcom Wi-Fi section]].)

== iwd ==

[[Iwd]] (iNet wireless daemon) is a wireless daemon written by Intel and aiming at replacing {{Pkg|wpa_supplicant}}. The core goal of the project is to optimize resource utilization by not depending on any external libraries and instead utilizing features provided by the Linux Kernel to the maximum extent possible.

{{Pkg|iwd}} is supported since [https://alpinelinux.org/posts/Alpine-3.10.0-released.html Alpine Linux 3.10].

To get started, install {{Pkg|iwd}}:

{{Cmd|# apk add iwd}}

To do anything with iwd, it has to be running:

{{Cmd|# rc-service iwd start}}

If it was not running, running <code>iwctl ..</code> commands will print

The name net.connman.iwd was not provided by any .service files
Failed to retrieve IWD dbus objects, quitting...

and running just <code>iwctl</code> will say it is waiting for IWD to start.

List your available wifi device(s) (you probably have ''wlan0''):

{{Cmd|$ iwctl device list}}

If you don't know the SSID of your network you can run a scan and retrieve a list of all the detected networks:

{{Cmd|$ iwctl station wlan0 scan && iwctl station wlp8s0 get-networks}}

To connect to a network:

{{Cmd|$ iwctl station wlan0 connect <SSID>}}

 

{{Note|iwd automatically stores network passphrases in the /var/lib/iwd directory and uses them to auto-connect in the future. If you run diskless Alpine, make sure to include this directory to the apkovl and commit:
{{Cmd|# lbu add /var/lib/iwd && lbu commit -d}}}}

{{Note|Since version 1.10, iwd supports IPv6, but it is disabled by default. To enable it, add the following to the configuration file:
{{Cat|/etc/iwd/main.conf|<nowiki>[Network]
EnableIPv6=true</nowiki>}}}}

 

Finally, configure {{Pkg|iwd}} and its dependency {{Pkg|dbus}} to start automatically on boot:
{{Cmd|# rc-update add iwd boot && rc-update add dbus boot}}

 

Add a entry for the desired interface (e.g. {{Path|wlan0}}):
{{Cat|/etc/network/interfaces|auto wlan0
iface wlan0 inet dhcp}}

{{Note|You could instead use the iwd's built-in network configuration by setting <code>EnableNetworkConfiguration{{=}}true</code> in {{Path|/etc/iwd/main.conf}}
{{Cat|/etc/iwd/main.conf|#[General]
...
EnableNetworkConfiguration{{=}}True
...}}
}}

 

Manually restart '''networking''':

{{Cmd|# rc-service networking restart}}

 

Your wifi interface should now be up and have a dedicated IP adress:
{{Cmd|$ ip a show wlan0}}

 

Useful link: [https://wiki.archlinux.org/title/Iwd#Enable_built-in_network_configuration Archlinux wiki page] if you need more specific configuration.

== wpa_supplicant ==

To get started install {{Pkg|wpa_supplicant}}

{{Cmd|# apk add wpa_supplicant}}

 

To list your available network interfaces:
{{Note|if you don't see any wireless interfaces (e.g. {{Path|wlan0}}), you probably need to load and/or install drivers/firmware.}}

 

{{Cmd|ip link}}
or
{{Cmd|ip a}}

 

Bring up the desired interface:
{{Cmd|# ip link set wlan0 up}}

{{Note|If this errors with <code>ioctl 0x8914 failed: No error information</code>, that's <code>busybox ip</code>'s way of saying your wireless radio is rfkill'd. See the [[#Rfkill|Rfkill section]] for information on how to unblock your wireless radio.}}

 

Use this command to add your Wi-Fi network to wpa_supplicant:
{{Cmd|# wpa_passphrase 'ExampleWifiSSID' 'ExampleWifiPassword' > /etc/wpa_supplicant/wpa_supplicant.conf}}
''(Access point not broadcasting its SSID requires additional line <code>scan_ssid=1</code> in the file <code>wpa_supplicant.conf</code>)''

{{Note|the Wi-Fi SSID and password are case sensitive and the single quote before and after the SSID and password need to be there}}

 

Start wpa_supplicant in the foreground to make sure the connection succeeds.
{{Cmd|# wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}

 

If all is well, run it as a daemon in the background by setting the {{Path|-B}} option.
{{Cmd|# wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf}}

 

Configure the interface with an IP address.
{{Cmd|# udhcpc -i wlan0}}

Sanity check: the interface should have a {{Path|inet}} address.
{{Cmd|$ ip addr show wlan0}}

 

=== Automatic Configuration on System Boot ===

Add a entry for the desired interface (e.g. {{Path|wlan0}}):
{{Cat|/etc/network/interfaces|auto wlan0
iface wlan0 inet dhcp}}

{{Note|Dont remove or comment out the '''auto lo''' entry}}

Sanity check: Make sure {{Path|/etc/wpa_supplicant/wpa_supplicant.conf}} is the correct configuration for the wireless access point you want to connect to.

Bring the interface down.

{{Cmd|# ip link set wlan0 down}}

 

Manually restart (or '''start''') '''networking'''.

{{Cmd|# /etc/init.d/networking --quiet restart &}}

 

If all is well (feel free to confirm with the sanity checks),

Configure wpa_supplicant to start automatically on boot:

{{Cmd|# rc-update add wpa_supplicant boot}}

 

Also make sure '''networking''' is set to automatically start on boot:

{{Cmd|# rc-update add networking boot}}

 

'''Optional security precaution:'''

By default {{Pkg|wpa_supplicant}} will store your Wi-Fi password in plain text:

{{Cat|(Example) /etc/wpa_supplicant/wpa_supplicant.conf|<nowiki>network={
ssid="<YourSSIDShouldBeHere>"
#psk="<YourPasswordShouldBeHereInPlainText>"
psk=<RandomLettersAndNumbersShouldBeHere>
}</nowiki>}}

this is not necessary and {{Pkg|wpa_supplicant}} should funtion just fine without it, if you dont want your stored password in plain text just delete the line with <code>#psk="<YourPasswordShouldBeHereInPlainText>"</code> on it.

 

== Launching udhcpc through wpa_cli actions ==

{{Todo|Figure out if theses two sections are different or connected to one another}}

With the above configuration, udhcpc will only run once at boot.
If the Wifi isn't available then, or the network changes in between, it needs to be notified.
This is done through the wpa_cli action script in /etc/wpa_supplicant/wpa_cli.sh

== Automatic Reconnection when WIFI signal is lost ==
To enable automatic reconnection when wifi signal is lost add these to config:

{{Cat|/etc/wpa_supplicant/wpa_supplicant.conf|<nowiki>ap_scan=1
autoscan=periodic:10
disable_scan_offload=1
</nowiki>
}}

{{Cmd|# rc-update add wpa_cli boot}}

 

== Troubleshooting ==

==== Broadcom Wi-Fi Chipset Users ====

The Broadcom chipset is quite popular among older computers. The b43 driver is included in the linux-lts or linux-edge kernel packages. However, you might need to compile the firmware manually for this chipset as it is not included in linux-firmware for some cargs.

You can check if you have a Broadcom chipset by using lspci:

{{Cmd|$ lspci -nn -d 14e4:}}

Now we need fwcutter:

{{Cmd|# apk add b43-fwcutter}}

Now we have everything to download the proprietary driver and extract the firmware from it:

{{Cmd|<nowiki># export FIRMWARE_INSTALL_DIR="/lib/firmware"
$ wget http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
$ tar xjf broadcom-wl-5.100.138.tar.bz2
# b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" broadcom-wl-5.100.138/linux/wl_apsta.o</nowiki>}}

More information can be found [http://linuxwireless.sipsolutions.net/en/users/Drivers/b43/#Other_distributions_not_mentioned_above here].

Now you need to use modprobe so the device will show up:

{{Cmd|# modprobe b43}}

Now continue with the normal instructions.

 

==== Rfkill ====

''See Also: [https://wiki.archlinux.org/title/Network_configuration/Wireless#Rfkill_caveat Network configuration/Wireless#Rfkill caveat - ArchLinux Wiki]''

 

Many laptops have a hardware button (or switch) to turn off wireless card, however, the card can also be blocked by kernel. This can be changed using rfkill. To show the current of your Wi-Fi:

~'''$''' rfkill list
0: phy0: wlan
Soft blocked: no
Hard blocked: no


 

If the card is hard-blocked, use the hardware button or switch to unblock it. If the card is not hard-blocked but soft-blocked, use the following command:

{{Cmd|# rfkill unblock wifi}}

 

== See Also ==

* [[Installation#Post-Install|Post Install]]
* [[Alpine setup scripts]]
* [[Iwd|iwd]]

[[Category:Networking]]

Bluetooth

2023-06-27T09:57:22Z

Bbbhltz: /* Troubleshooting */ added tip for automatic audio output switching

{{Draft|work in progress}}

[https://en.wikipedia.org/wiki/Bluetooth Bluetooth] is a standard for the short-range wireless interconnection of cellular phones, computers, and other electronic devices. [http://www.bluez.org/ BlueZ] is an implementation of the Bluetooth protocol stack for Linux, and it is provided by the {{Pkg|bluez}} package.

This article describes the basic installation of Bluetooth controllers and devices.

== Prerequisites and Basic Installation ==

=== Prerequisites ===

{{Pkg|eudev}} should be installed and setup:

{{Cmd|# setup-devd udev}}

=== Basic Installation ===

Basic installation is as follows:

# Install {{Pkg|bluez}}
#* Optionally install {{Pkg|bluez-deprecated}} if you need deprecated tools like <code>hcitool</code>
# Load the <code>btusb</code> kernel module
# Add user to the <code>lp</code> group
# Start and enable the Bluetooth service

{{Cmd|# apk add bluez
# apk add bluez-deprecated
# modprobe btusb
# adduser $USER lp
# rc-service bluetooth start
# rc-update add bluetooth default}}

Now, check the state of the Bluetooth radio transmitter using <code>rfkill</code>:

{{Cmd|$ rfkill list bluetooth}}

It should return something similar to:

0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

If the device is listed as blocked, it can be unblocked using the same tool:

{{Cmd|# rfkill unblock bluetooth}}

{{Note|It may be necessary to restart the Bluetooth service before continuing.}}

=== Front-ends ===

There are several front-ends available:

* The {{Pkg|bluez}} comes with the <code>bluetoothctl</code> front-end
* {{Pkg|blueman}}: a full-featured Bluetooth manager
* {{Pkg|bluedevil}}: the [[KDE]] Bluetooth manager
* {{Pkg|gnome-bluetooth}}: the [[Gnome]] Bluetooth manager

== Pairing ==

=== Using <code>bluetoothctl</code> ===

Begin by starting <code>bluetoothctl</code> and follow these basic steps:

{{Cmd|$ bluetoothctl}}

The prompt should display:

[bluetooth]#

List the available controllers:

[bluetooth]# list

Display information about a controller:

[bluetooth]# show ''controller_mac_address''

Set the default controller:

[bluetooth]# select ''controller_mac_address''

Power on the controller:

[bluetooth]# power on

Enable the agent and set it as default:

[bluetooth]# agent on
[bluetooth]# default-agent

Set the controller as discoverable (temporarily for 3 minutes) and pairable:

[bluetooth]# discoverable on
[bluetooth]# pairable on

Scan for devices:

[bluetooth]# scan on

Put the device into pairing mode. This generally involves pressing a button or a combinations of buttons, usually for several seconds.

Discover the device MAC address:

[bluetooth]# devices

Pair with the device:

[bluetooth]# pair ''device_mac_address''

Enter the PIN if prompted:

[agent] PIN code: ####

Trust the device:

[bluetooth]# #trust ''device_mac_address''

Connect to the device:

[bluetooth]# connect ''device_mac_address''

Display information about the device:

[bluetooth]# info ''device_mac_address''

The device is now paired:

[bluetooth]# quit

== Configuration ==

=== Set adapter power state ===

If you would like the adapter to not be automatically enabled (e.g. on a portable device where you wish to save battery), set <code>AutoEnable=false</code> in <code>/etc/bluetooth/main.conf</code> in the <code>[Policy]</code> section:

{{Cat|/etc/bluetooth/main.conf|[Policy]
...
AutoEnable=false
...}}

=== Battery Reporting ===

An experimental feature can be enabled in order to report device battery level:

{{Cat|/etc/bluetooth/main.conf|[General]
...
Experimental=true
...}}

== Troubleshooting ==

Due to the variety of available Bluetooth hardware it is possible that you receive errors while attempting to install, activate, or find your Bluetooth device.

=== "No default controller available" error ===

After having followed these instructions, or others, you run <code>bluetoothctl</code> and encounter the following scenario:

[bluetooth]# list
[bluetooth]# show
No default controller available

One possible solution is that you are missing firmware drivers.

Try running the following command to discover the source of the issue:

{{Cmd|# dmesg | grep -i bluetooth | grep -i firmware}}

There are many firmware packages available that could likely solve the this problem (see {{Pkg|linux-firmware-*}}).

Another possible solution is to install {{Pkg|hidapi}} and add load the module:

{{Cmd|# apk add hidapi
# modprobe uhid}}

=== Unable to control Bluetooth speaker volume / Bluetooth output is muted (Pulseaudio) ===

It is possible to automatically switch audio output and volume control to last connected device.

This can solve the problem of controlling the speaker volume when switching between Bluetooth devices.

Append the following lines at the end of the {{Path|/etc/pulse/default.pa}}:

{{Cat|/etc/pulse/default.pa|...
###Automatically switch audio to the most recently connected device (Bluetooth, HDMI, USB)
load-module module-switch-on-connect}}

== See Also ==

* [[Bluetooth_audio|Bluetooth Audio]] page
* [https://wiki.gentoo.org/wiki/Bluetooth Bluetooth entry on Gentoo Wiki]
* [https://wiki.archlinux.org/title/Bluetooth Bluetooth entry on ArchWiki]

[[Category:Multimedia]]
[[Category:Hardware]]
[[Category:Newbie]]

Category:Web Browser

2023-06-07T17:19:22Z

Bbbhltz: Removed midori

A web browser is an application for accessing websites. When a user requests a web page from a particular website, the browser retrieves its files from a web server and then displays the page on the user’s screen.

Alpine Linux packages several web browsers.

== Console ==

* '''Elinks''' {{Pkg|elinks}}: feature-rich text mode web browser
* '''Links''' {{Pkg|links}}/{{Pkg|links-graphics}}: web browser with both graphics and text mode
* '''Lynx''' {{Pkg|lynx}}: text-based browser
* '''w3m''' {{Pkg|w3m}}: text-based web & gopher browser, as well as pager

== Graphical ==

* '''Badwolf''' {{Pkg|badwolf}}: A minimalist and privacy-oriented WebKit browser
* '''Chromium''' {{Pkg|chromium}}: the open source project behind Google Chrome, Blink-based
* '''Dillo''' {{Pkg|dillo}}: small and fast GUI web browser
* '''Epiphany/GNOME Web''' {{Pkg|epiphany}}: GNOME's WebKitGTK-based browser
* '''[[Firefox]]''': browser from Mozilla based on Gecko with fast rendering
* '''Netsurf''' {{Pkg|netsurf}}: an open source web browser
* '''Nyxt''' {{Pkg|nyxt}}: the ''“hacker’s browser”''
* '''Qutebrowser''' {{Pkg|qutebrowser}}: keyboard-driven, Vim-like browser based on PyQT5
* '''Surf''' {{Pkg|surf}}: a simple web browser based on WebKit2/GTK+
* '''Tor''' {{Pkg|tor}}: a modified Mozilla Firefox ESR web browser used for accessing the Tor network — usually not recommended for general web browsing
* '''Vieb''' {{Pkg|vieb}}: Vim-inspired Electron browser
* '''Vimb''' {{Pkg|vimb}}: a Vim-like browser

[[category: Desktop]]

Template:AlpineLatest

2023-06-07T13:33:57Z

Bbbhltz: Version change to 3.18.0

<noinclude>{{Template}}
</noinclude>3.18.0

Alpine Linux talk:FAQ

2023-06-06T07:13:14Z

Bbbhltz: /* Package requests */ new section

=== How can I install a custom firmware in a diskless system? ===

''After reboot Alpine should automatically use the directory on your local storage instead of the loopback device.''

Is this correct? What is the underlying mechanism for detecting this? Should we supply a bit more detail?

=== How do I set the local timezone? ===

This answer targets uClibc. Should be updated to explain we no longer use that libc.

-- [[User:Dubiousjim|Dubiousjim]] ([[User talk:Dubiousjim|talk]]) 13:11, 17 January 2015 (UTC)

== Is there a port of LXDE/LXQt? ==

Is there a port of LXDE/LXQt? I'd like to run it in Alpine instead of XFCE.

== Package requests ==

Is there an easy way to filter or search the GitLab issues for packages that have been requested and refused?

I know that many Chromium and Firefox forks are refused for good reasons (e.g. LibreWolf, Ungoogled Chromium, and Brave).

[[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 07:13, 6 June 2023 (UTC)

Talk:Setting up a laptop

2023-06-06T06:02:29Z

Bbbhltz: /* Status of page */ spaces

Please add [[UEFI Secure Boot]] to this page. --[[User:Jirutka|Jirutka]] ([[User talk:Jirutka|talk]]) 21:05, 11 September 2022 (UTC)

<hr>

<blockquote>
ACPI is a good '''daemon''' to use to execute certain scripts when laptop events are triggered.
To install ACPI do: apk add acpi
</blockquote>
Package {{pkg|acpi}} provides an ACPI client, not a daemon. The daemon is provided either by {{pkg|busybox}} or {{pkg|acpid}}.

== Status of page ==

When is the completion of this page (removal of warning banner) anticipated?

:Test out the instructions and see if they work I guess? If all goes well remove the Draft tag. [[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 06:01, 6 June 2023 (UTC)

Talk:Setting up a laptop

2023-06-06T06:01:54Z

Bbbhltz: /* Status of page */ reply

Please add [[UEFI Secure Boot]] to this page. --[[User:Jirutka|Jirutka]] ([[User talk:Jirutka|talk]]) 21:05, 11 September 2022 (UTC)

<hr>

<blockquote>
ACPI is a good '''daemon''' to use to execute certain scripts when laptop events are triggered.
To install ACPI do: apk add acpi
</blockquote>
Package {{pkg|acpi}} provides an ACPI client, not a daemon. The daemon is provided either by {{pkg|busybox}} or {{pkg|acpid}}.

== Status of page ==

When is the completion of this page (removal of warning banner) anticipated?

:Test out the instructions and see if they work I guess? If all goes well remove the Draft tag.[[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 06:01, 6 June 2023 (UTC)

Iwd

2023-06-05T20:55:48Z

Bbbhltz: basic information and configuration

{{DISPLAYTITLE:iwd}}

iwd ('''i'''Net '''W'''ireless '''D'''aemon) is a wireless daemon for Linux. It is written by Intel and aims to replace <code>wpa_supplicant</code>. The core goal of the project is to optimize resource utilization: storage, runtime memory and link-time costs. This is accomplished by not depending on any external libraries and utilizes features provided by the Linux Kernel to the maximum extent possible. The result is a self-contained environment that only depends on the Linux Kernel and the runtime C library.

Potential benefits of iwd include:

* simplification of network management
* faster network discovery
* fast and reliable roaming
* using less system resources
* using features offered by the Linux kernel
* support for enterprise security methods like EAP
* support for kernel asymmetric key rings and [https://en.wikipedia.org/wiki/Trusted_Platform_Module Trusted Platform Modules (TPM)]
* support for multiple clients

== Installation ==

Install <code>iwd</code>:

{{Cmd|# apk add {{Pkg|iwd}}}}

== Usage (iwctl) ==

The iwd package provides the client program <code>iwctl</code>, the daemon <code>iwd</code> and the Wi-Fi monitoring tool <code>iwmon</code>.

Begin by starting the client:

{{Cmd|$ iwctl}}

To list all available commands:

[iwd]# help

=== Connect to a network ===

First, if you do not know your wireless device name, list all Wi-Fi devices:

[iwd]# device list

If the device or its corresponding adapter is turned off, turn it on:

[iwd]# device ''device'' set-property Powered on

[iwd]# adapter ''adapter'' set-property Powered on

Then, to initiate a scan for networks (note that this command will not output anything):

[iwd]# station ''device'' scan

You can then list all available networks:

[iwd]# station ''device'' get-networks

Finally, to connect to a network:

[iwd]# station ''device'' connect ''SSID''

If a passphrase is required, you will be prompted to enter it. Alternatively, you can supply it as a command line argument:

{{Cmd|$ iwctl –passphrase ''passphrase'' station ''device'' connect ''SSID''}}

{{Note|
* iwd automatically stores network passphrases in the {{Path|/var/lib/iwd}} directory and uses them to auto-connect in the future.
* To connect to a network with spaces in the SSID, the network name should be double quoted when connecting.
* iwd only supports PSK pass-phrases from 8 to 63 ASCII-encoded characters. }}

=== Disconnect from a network ===

To disconnect from a network:

[iwd]# station ''device'' disconnect

=== Show device and connection information ===

To display the details of a WiFi device, like MAC address:

[iwd]# device ''device'' show

To display the connection state, including the connected network of a Wi-Fi device:

[iwd]# station ''device'' show

=== Manage known networks ===

To list networks you have connected to previously:

[iwd]# known-networks list

To forget a known network:

[iwd]# known-networks ''SSID'' forget

{{Note|It is not possible to assign a priority to a network, instead iwd will prioritize networks based on:

* signal strength level
* security features
* maximum rate
* channel utilization
* time since the last connect.}}

== Dedicated GUI (iwgtk) ==

[[File:Iwgtk screenshot.png|thumb|right|100px|alt=iwgtk showing list of networks|iwgtk]]

iwgtk is a wireless networking GUI for Linux with supported functionality similar to that of <code>iwctl</code>. Features include viewing and connecting to available networks, managing known networks, provisioning new networks via WPS or Wi-Fi Easy Connect, and an indicator (tray) icon displaying connection status and signal strength.

{{Cmd|# apk add {{Pkg|iwgtk}}}}

== Usage as a Backend ==

iwd can be used as a replacement backend for NetworkManager. See [[NetworkManager#iwd_backend|the relevant NetworkManager section]] for more information.

== See also ==

* [https://wiki.gentoo.org/wiki/Iwd iwd on Gentoo Wiki]
* [https://wiki.archlinux.org/title/Iwd iwd on ArchWiki]
* [https://iwd.wiki.kernel.org/start iwd Wiki]
* [https://github.com/J-Lentz/iwgtk iwgtk: Lightweight wireless networking GUI (front-end for iwd)]

[[Category:Networking]]

File:Iwgtk screenshot.png

2023-06-05T20:43:56Z

Bbbhltz:

iwgtk showing list of available networks as well as diagnostics windows

NetworkManager

2023-06-05T15:21:58Z

Bbbhltz: nmcli and nmtui have been split into separate packages

[https://networkmanager.dev/ NetworkManager] is a program that provides automatic detection and configuration for systems to connect to networks.

== Installation ==

{{Cmd|# apk add {{Pkg|networkmanager}}}}

 

There are multiple interfaces available for NetworkManager:

* TUI: {{Pkg|networkmanager-tui}}, a curses-based interface (run <code>nmtui</code>)
* Command line: {{Pkg|networkmanager-cli}} (run <code>nmcli</code>)
* GUI: {{Pkg|plasma-nm}} for Plasma integration and applet
* GUI: {{Pkg|network-manager-applet}} for a GTK system tray applet

 

You will need to install an additional package if you want NetworkManager to connect to wifi:
{{Cmd|# apk add {{Pkg|networkmanager-wifi}}}}

 

After installation start NetworkManager:
{{Cmd|# rc-service networkmanager start}}

 

Then set it to autostart the service on boot:
{{Cmd|# rc-update add networkmanager default}}

 

Also your user needs to be in the <code>plugdev</code> group:
{{Cmd|# adduser <YourUsername> plugdev}}

{{Note|you will need to log out for the new group to take effect}}

 

== Wireless networks ==

==== wpa_supplicant backend ====

{{Todo|([[KDE|KDE Plasma]] Desktop) find out if it is possible to prevent requesting the password for '''KDE Wallet''' on login}}

* Follow: [[Wi-Fi#wpa_supplicant]] and [[Wi-Fi#Automatic_Configuration_on_System_Boot]]
{{Note|{{Pkg|wpa_supplicant}} configuration might not be required, if it isnt it may be a good idea to have it setup just as a fallback}}

 

Now open <code>/etc/NetworkManager/NetworkManager.conf</code> in a text editor and change it to something like this:

{{Cat|/etc/NetworkManager/NetworkManager.conf|<nowiki>[main]
dhcp=internal
plugins=ifupdown,keyfile

[ifupdown]
managed=true

[device]
wifi.scan-rand-mac-address=yes
wifi.backend=wpa_supplicant</nowiki>}}

{{Note|if these options dont work on your system you can change them as necessary}}

 

Now you need to stop conflicting services:

{{Cmd|# rc-service networking stop}}
{{Cmd|# rc-service wpa_supplicant stop}}

 

Now restart NetworkManager:

{{Cmd|# rc-service networkmanager restart}}

 

Now connect to a network using one of the interfaces mentioned in [[NetworkManager#Installation|Installation]]

 

If that connects and stays connected with no issues enable the <code>networkmanager</code> service and disable the <code>networking</code> and <code>wpa_supplicant</code> boot services:

{{Cmd|# rc-update add networkmanager}}
{{Cmd|# rc-update del networking boot}}
{{Cmd|# rc-update del wpa_supplicant boot}}

 

==== iwd backend ====

NetworkManager supports wireless networks through {{Pkg|iwd}}, however, consider [https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues?scope=all&utf8=%E2%9C%93&state=opened&search=iwd existing issues] before using it. After installation, enable the server and restart NetworkManager:
<pre>
rc-service iwd start
rc-service networkmanager restart
</pre>

To use {{Pkg|iwd}} though, you've have to edit NetworkManager's configuration because it still defaults to {{Pkg|wpa_supplicant}} instead. Add the following to {{Path|/etc/NetworkManager/NetworkManager.conf}}:

<pre>
[device]
wifi.backend=iwd
</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

== nm-applet ==
=== not authorized to control networking ===

You can enable all users to edit connections without adding polkit.
First, make the <code>conf.d</code> directory for networkmanager:

{{Cmd|# mkdir -p /etc/NetworkManager/conf.d}}

Then, add following content to <code>/etc/NetworkManager/conf.d/any-user.conf</code>:

<pre>
[main]
auth-polkit=false
</pre>

Finally, restart networkmanager:

{{Cmd|# /etc/init.d/networkmanager restart}}

[[Category:Networking]]

Inotifyd

2023-06-01T19:52:45Z

Bbbhltz: /* Create an OpenRC service script */ remove extra spaces

== Use case ==

Sometimes we need to monitor a directory (or file) and do some post processing/actions. Instead of polling the directory for changes we can use inotify to watch a specific folder or file and be notified if something happens within its context. While there are tools in aports designed around inotify (inotify-tools) alpine has a build in tool called inotifyd (part of busybox) to execute a command on file system events. Below is an example of how you can setup a watch folder with just base alpine (busybox and openrc).

== Create an OpenRC service script ==

{{Cat|/etc/init.d/inotifyd|<nowiki>#!/sbin/openrc-run

command=/sbin/inotifyd
command_args="$INOTIFYD_ARGS"
command_user="$INOTIFYD_USER"
pidfile=/run/${RC_SVCNAME}.pid
command_background=yes
start_stop_daemon_args="--stdout /var/log/$RC_SVCNAME/${RC_SVCNAME}.log --stderr /var/log/$RC_SVCNAME/${RC_SVCNAME}.log"

start_pre() {
checkpath --directory --owner $INOTIFYD_USER --mode 0775 \
/var/log/$RC_SVCNAME
}</nowiki>}}

{{Cat|/etc/conf.d/inotifyd|<nowiki>INOTIFYD_ARGS="/usr/local/bin/myscript /home/username/watchdir:w"
INOTIFYD_USER=username</nowiki>}}

{{Cat|/usr/local/bin/myscript|<nowiki>#!/bin/sh

event="$1"
directory="$2"
file="$3"

# run some command based on an event
case "$event" in
w) echo "writable $file is closed in $directory";;
*) echo "This will never happen as we only listen for w.";;
esac</nowiki>}}

== Finishing up ==

Starting inotifyd:

{{Cmd|# rc-service inotifyd start}}

Now copy some file into the watch folder and check the service log in {{Path|/var/log/inotifyd}}.

In the example above we only listen for file closed events (w). In case you want to listen to more events you can just add them after each other. In case you want to listen to all of them you simply remove all appending event letters from the directory.

== Possible inotify Events ==

<pre>
Events:
a File is accessed
c File is modified
e Metadata changed
w Writable file is closed
0 Unwritable file is closed
r File is opened
D File is deleted
M File is moved
u Backing fs is unmounted
o Event queue overflowed
x File can't be watched anymore
If watching a directory:
y Subfile is moved into dir
m Subfile is moved out of dir
n Subfile is created
d Subfile is deleted
</pre>

[[Category:Monitoring]]

Inotifyd

2023-06-01T19:52:14Z

Bbbhltz: style changes

== Use case ==

Sometimes we need to monitor a directory (or file) and do some post processing/actions. Instead of polling the directory for changes we can use inotify to watch a specific folder or file and be notified if something happens within its context. While there are tools in aports designed around inotify (inotify-tools) alpine has a build in tool called inotifyd (part of busybox) to execute a command on file system events. Below is an example of how you can setup a watch folder with just base alpine (busybox and openrc).

== Create an OpenRC service script ==

{{Cat|/etc/init.d/inotifyd|<nowiki>#!/sbin/openrc-run

command=/sbin/inotifyd
command_args="$INOTIFYD_ARGS"
command_user="$INOTIFYD_USER"
pidfile=/run/${RC_SVCNAME}.pid
command_background=yes
start_stop_daemon_args="--stdout /var/log/$RC_SVCNAME/${RC_SVCNAME}.log --stderr /var/log/$RC_SVCNAME/${RC_SVCNAME}.log"

start_pre() {
checkpath --directory --owner $INOTIFYD_USER --mode 0775 \
/var/log/$RC_SVCNAME
}</nowiki>}}

{{Cat|/etc/conf.d/inotifyd|<nowiki>INOTIFYD_ARGS="/usr/local/bin/myscript /home/username/watchdir:w"
INOTIFYD_USER=username</nowiki>}}

{{Cat|/usr/local/bin/myscript|<nowiki>#!/bin/sh

event="$1"
directory="$2"
file="$3"

# run some command based on an event
case "$event" in
w) echo "writable $file is closed in $directory";;
*) echo "This will never happen as we only listen for w.";;
esac

</nowiki>}}

== Finishing up ==

Starting inotifyd:

{{Cmd|# rc-service inotifyd start}}

Now copy some file into the watch folder and check the service log in {{Path|/var/log/inotifyd}}.

In the example above we only listen for file closed events (w). In case you want to listen to more events you can just add them after each other. In case you want to listen to all of them you simply remove all appending event letters from the directory.

== Possible inotify Events ==

<pre>
Events:
a File is accessed
c File is modified
e Metadata changed
w Writable file is closed
0 Unwritable file is closed
r File is opened
D File is deleted
M File is moved
u Backing fs is unmounted
o Event queue overflowed
x File can't be watched anymore
If watching a directory:
y Subfile is moved into dir
m Subfile is moved out of dir
n Subfile is created
d Subfile is deleted
</pre>

[[Category:Monitoring]]

Raspberry Pi 3 - Setting Up Bluetooth

2023-06-01T19:47:31Z

Bbbhltz: proposal to merge, style tweaks

{{Merge|Raspberry Pi|or create subpages}}

The Raspberry Pi Bluetooth chip varies by model.

* Raspberry Pi 3 has BCM2837 connected to the hardware UART
* Raspberry Pi 3B+ has BCM4345C0 connected to the hardware UART
* Raspberry Pi Zero W has BCM43430A1 connected to the hardware UART

You can get Bluetooth to work only if you are not using the UART (ttyAMA0) for anything else, for example serial console.
Recent versions of Alpine Linux for Raspberry Pi come with the required Broadcom firmware files.
If you need the UART for something else, you can use an USB Bluetooth adapter instead.

You'll need the bluez package

{{cmd|# apk add bluez}}

The Bluetooth controller is not automatically discovered on the UART. Test attaching it and check that the controller is found:

{{cmd|$ btattach -B /dev/ttyAMA0 -P bcm -S 115200 -N &}}

{{cmd|# rc-service bluetooth start}}

~'''$''' bluetoothctl list

Controller B8:27:EB:01:02:03 BlueZ 5.50 [default]


If the interface is discovered after the attach, you can make attaching persistent by uncommenting
the line next to <code>rpi bluetooth</code> in {{Path|/etc/mdev.conf}}.

Start the Bluetooth daemon at boot:

{{cmd|# rc-update add bluetooth}}

{{cmd|# lbu commit && reboot}}

The output from the <code>btattach</code> above should be

Attaching Primary controller to /dev/ttyAMA0
Switched line discipline from 0 to 15
Device index 0 attached

Then it's a matter of doing what you normally do with your Bluetooth stack.

== See also ==

* [[Bluetooth]]

[[Category:Installation]]
[[category: Raspberry]]

Elogind

2023-06-01T19:41:09Z

Bbbhltz: added to Desktop category, minor style changes

[https://github.com/elogind/elogind '''elogind'''] is a login manager and provides support for

* setting up necessary permissions for the desktop environment or window manager
* handling poweroff, reboot, suspend and hibernate via '''loginctl''' command

== Installation ==

{{Cmd|# apk add {{Pkg|elogind}} {{Pkg|polkit-elogind}}
# rc-update add elogind
# rc-service elogind start}}

== Configuration ==

=== logind.conf ===

Edit {{Path|/etc/elogind/logind.conf}} to configure handling of power events, such as suspending the computer when power button is pressed:

{{Cmd|<nowiki># sed -i 's|#HandlePowerKey=poweroff|HandlePowerKey=suspend|' /etc/elogind/logind.conf</nowiki>}}

=== Working with Desktop Environments ===

If using a Window Manager or Desktop Environment, such as [[Sway]], the user must ensure that login session is correctly configured. When correctly configured, the <code>loginctl</code> command should output the following:

'''Using [[Sway]] and [[SDDM]]'''

~'''$''' loginctl

SESSION UID USER SEAT TTY
c1 105 sddm seat0
c2 1000 User seat0 tty8

2 sessions listed.


If the output is <code>No session available.</code>, such as in the case of launching Sway from tty, suspend and many other functionality will not work. The user then must configure a display manager such as {{Pkg|greetd}}, [[SDDM]] or {{Pkg|lightdm|LightDM}}.

== See also ==

* [https://wiki.gentoo.org/wiki/Elogind elogind - Gentoo Wiki]

[[Category:Desktop]]

Sending SMS using gnokii

2023-06-01T14:53:21Z

Bbbhltz: marked for deletion: gnokii is no longer in the repositories

__NOTOC__

{{Delete|gnokii is no longer in the repositories}}

In this tutorial we are using {{pkg|gnokii}} to send SMS

== Prerequisites ==
This doc is documented and tested based on Alpine Linux 2.7, but it might work for earlier versions too. 
You will also need some sort of modem that can send SMS (e.g. a USB dongle with a SIM-card).

== Install ==
* Install required package(s)
{{Cmd|apk add gnokii}}
* Create missing folders
{{Cmd|mkdir -p /root/.cache/gnokii/}}
* Physically attach a SMS capable modem to the host

== Configure ==
* Add the following content to '<tt>/etc/gnokiirc</tt>'
<pre>
[global]
port = /dev/ttyUSB0
model = AT
connection = serial
use_locking = yes
serial_baudrate = 115200
smsc_timeout = 30

[gnokiid]
binddir = /usr/bin/

[logging]
debug = off
rlpdebug = off
xdebug = off
</pre>
{{Note|You will most likely need to change the above config so it to suit your equipment and setup.}}
* Verify if the configuration works as expected
{{cmd|gnokii --identify}}
{{note|You should receive a output that looks something like this:<pre>
GNOKII Version 0.6.31
Cannot open logfile /root/.cache/gnokii/gnokii-errors
WARNING: cannot open logfile, logs will be directed to stderr
IMEI : 123456789012345
Manufacturer : Undefined
No flags section in the config file.
Model : Teltonika TM1
Product name : Teltonika TM1
Revision : VilniusSMD 05.94.01
</pre>
}}

== Sending SMS ==
* Now send a SMS
{{cmd|echo "Test sms" {{!}} gnokii --sendsms 123456}}
{{note|You will need to replace 123456 with the phone number you want to send your test SMS}}

[[Category:Software]]

Sircbot

2023-06-01T11:44:11Z

Bbbhltz: style and formatting

Sircbot is a Minimalistic IRC bot based in Lua script.

== Install sircbot ==

{{Cmd|# apk add {{Pkg|sircbot}} {{Pkg|lua-sircbot}}}}

== Configure sircbot ==

Edit the configuration file located at {{Path|/etc/conf.d/sircbot}} and change the name, server, and channel:

{{Cat|/etc/conf.d/sircbot|...
sircbot_opts{{=}}"-n name -s server"
sircbot_channels{{=}}"#channel"
...}}

== Create sircbot scripts folders and files ==

Sircbot will use an folder for the channel where is logged in. Lets say we will use it at the "test" channel.
The folder path is: {{Path|/etc/sircbot.d/#channel}}

== Example ==

Lets see an example:

Our bot will be named ''kumquat'' and we will join at the #test channel in the irc.ddd.ddd server.

{{Cat|/etc/conf.d/sircbot|sircbot_opts{{=}}"-n kumquat -s irc.ddd.ddd"
sircbot_channels{{=}}"#test"}}

Create folder bot.

{{Cmd|# mkdir /etc/sircbot.d/#test -p}}

Create the Lua script file for our bot.

{{Cat|/etc/sircbot.d/#test/commands|<nowiki>#!/usr/bin/lua

-- Scripts for kumquat in Lua

args={...}

sender=args[1] -- is the nickname of running the command on IRC
message=args[2] -- is the message or command typed
channel=args[3] -- is the channel name

os.execute("sleep " .. tonumber(1))

-- This command will show: What can i do for you "nickname"?
local kumquatresult = string.find(message, "kumquat")
if kumquatresult ~= nil then
command="echo 'What can i do for you '"..sender.."'?' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show: Hello there, amigo "nickname"
local kumquatresult = string.find(message, "hi")
if kumquatresult ~= nil then
command="echo 'Hello there, amigo '"..sender.."'' | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will show the current UTC date and time
local kumquatresult = string.find(message, "date")
if kumquatresult ~= nil then
command="date -u | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a search for a alpine linux package
local kumquatresult = string.find(message, "apk search:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 12))
command="apk search"..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will resolve a host name and ip
local kumquatresult = string.find(message, "host:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="host "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end

-- This command will do a 3 times ping to a server or ip address
local kumquatresult = string.find(message, "ping:[^%d]")
if kumquatresult ~= nil then
local strng = (string.sub(message, 6))
command="ping -c 3 "..strng.." | sircbot-send '"..channel.."'"
io.popen(command)
end</nowiki>}}

Make the script to be executable

{{Cmd|# chmod +x /etc/sircbot.d/#test/commands}}

== Giving life to the bot ==

Starting bot service and adding to boot.

{{Cmd|# rc-service sircbot start && rc-update add sircbot default}}

== Troubleshooting ==

If your bot is not responding as expected, an easy way to troubleshoot is to manually execute the script in /etc/sircbot.d/<#channelname>/<scriptname> with the three agruments.

{{Cmd|$ /etc/sircbot.d/<#channelname>/<scriptname> username hi '<#channelname>'}}

If your bot responds as expected, then you know that your script works. The problem is that sircbot is not executing the script. Here are two likely causes:

# Sircbot is case-sensitive when looking for the channel directory for a script to execute. For example, if you have a channel named "#Alpine", sircbot will look for /etc/sircbot.d/#Alpine/*. If that pathway isn't exactly right, then sircbot will skip that folder. In our example, if you have /etc/sircbot.d/#alpine/script, sircbot will not execute anything in that folder. To fix, simply rename the folder to /etc/sircbot.d/#Alpine/
# Sircbot doesn't execute scripts that have a '.' in the name. For example a script named 'listen.lua' will not be executed. Simply rename the script to 'listen'.

[[Category:Networking]]

Flatpak

2023-06-01T09:25:50Z

Bbbhltz: style tweaks

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snap_(software) Snap],

== Setup / Installation ==

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add {{Pkg|flatpak}}}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|$ flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

== Usage ==

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

=== Search ===

To search for applications run '''flatpak search <appplicationname>'''

Example:

~'''$''' flatpak search chromium

Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub


 

=== Install ===

To install a package run '''flatpak install <applicationname>'''

~'''$''' flatpak install com.github.Eloston.UngoogledChromium

Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:


or if you dont know or dont want to type the exact package name:

~'''$''' flatpak install chromium

Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:


=== Remove ===

To remove a package run: '''flatpak remove <applicationname>'''

~'''$''' flatpak remove com.github.Eloston.UngoogledChromium

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:


or if you dont know or dont want to type the exact package name:

~'''$''' flatpak remove chromium

Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:


== Developers ==

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

== Troubleshooting ==

=== Permission errors ===

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group.

{{Note|You need to log out and log back in or reboot for the group change(s) to take effect}}

=== Fixing audio issues ===

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in {{Path|/etc/profile.d/xdg_runtime_dir.sh}} and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:

{{Cmd|$ pulseaudio --start && flatpak run com.example.Example}}

== Links ==
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

[[Category:Package Manager]]
[[Category: Desktop]]

Flatpak

2023-06-01T09:16:47Z

Bbbhltz: /* Search */ style tweak

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snap_(software) Snap],

== Setup / Installation ==

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add {{Pkg|flatpak}}}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|$ flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

== Usage ==

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

=== Search ===

To search for applications run '''flatpak search <appplicationname>'''

Example:

~'''$''' flatpak search chromium
Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub


 

=== Install ===

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

=== Remove ===

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

== Developers ==

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

== Troubleshooting ==

=== Permission errors ===

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group.

{{Note|You need to log out and log back in or reboot for the group change(s) to take effect}}

=== Fixing audio issues ===

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in {{Path|/etc/profile.d/xdg_runtime_dir.sh}} and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:

{{Cmd|$ pulseaudio --start && flatpak run com.example.Example}}

== Links ==
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

[[Category:Package Manager]]
[[Category: Desktop]]

User:Bbbhltz/learntowiki

2023-06-01T09:14:07Z

Bbbhltz: making a subpage

~'''$''' flatpak search chromium
Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub

Flatpak

2023-06-01T08:31:25Z

Bbbhltz: some small formatting changes, content unchanged

{{Draft|More documentation and testing is needed, but everything currently here should be safe to follow.}}

Flatpak is a technology for building and distributing applications with the goal of having a universal package format for all Linux distributons, it is similar to [https://en.wikipedia.org/wiki/Snap_(software) Snap],

== Setup / Installation ==

''From: https://flatpak.org/setup/Alpine/''

{{Note|To install Flatpak you will need to enable the Community repository, See: [[Repositories#Managing_repositories|Repositories - Managing repositories]]}}

To install Flatpak run:

{{cmd|# apk add {{Pkg|flatpak}}}}

Next you need to add a repository, for this guide we will use the recommended repository, [https://flathub.org Flathub].

{{cmd|$ flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo}}

Now reboot to complete setup

{{Note|graphical installation of Flatpak apps may not be possible with Alpine.}}

== Usage ==

To get all of the available options to use with the '''flatpak''' command run: '''flatpak --help''' or '''flatpak -h''',

=== Search ===

To search for applications run '''flatpak search <appplicationname>'''

Example:

{{cat|$ flatpak search chromium|Name Description Application ID Version Branch Remotes
Chromium Web Browser The web browser from Chromium project org.chromium.Chromium 96.0.4664.93 stable flathub
Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable flathub
ungoogled-chromium A lightweight approach to removing Google web service dependency com.github.Eloston.UngoogledChromium 96.0.4664.45 stable flathub}}

 

=== Install ===

To install a package run '''flatpak install <applicationname>'''

{{cat|$ flatpak install com.github.Eloston.UngoogledChromium|Looking for matches…

com.github.Eloston.UngoogledChromium permissions:
ipc network cups pulseaudio wayland x11
devices file access [1] dbus access [2] bus ownership [3] system dbus access [4]

[1] /run/.heim_org.h5l.kcm-socket, home, xdg-run/pipewire-0
[2] org.freedesktop.FileManager1, org.freedesktop.Notifications, org.freedesktop.secrets, org.gnome.SessionManager
[3] org.mpris.MediaPlayer2.chromium.*
[4] org.freedesktop.Avahi, org.freedesktop.UPower

ID Branch Op Remote Download
1. com.github.Eloston.UngoogledChromium.Codecs stable i flathub < 1.1 MB
2. com.github.Eloston.UngoogledChromium.Locale stable i flathub < 112.8 kB
3. com.github.Eloston.UngoogledChromium stable i flathub < 119.0 MB

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak install chromium|Looking for matches…
Similar refs found for ‘chromium’ in remote ‘flathub’ (system):

1) app/net.sourceforge.chromium-bsu/x86_64/stable
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable
3) runtime/org.chromium.Chromium.Codecs/x86_64/stable
4) app/org.chromium.Chromium/x86_64/stable
5) app/com.github.Eloston.UngoogledChromium/x86_64/stable

Which do you want to use (0 to abort)? [0-5]:}}

=== Remove ===

To remove a package run: '''flatpak remove <applicationname>'''

{{cat|$ flatpak remove com.github.Eloston.UngoogledChromium|

ID Branch Op
1. com.github.Eloston.UngoogledChromium stable r
2. com.github.Eloston.UngoogledChromium.Codecs stable r
3. com.github.Eloston.UngoogledChromium.Locale stable r

Proceed with these changes to the system installation? [Y/n]:}}

or if you dont know or dont want to type the exact package name:

{{cat|$ flatpak remove chromium|Similar installed refs found for ‘chromium’:

1) app/com.github.Eloston.UngoogledChromium/x86_64/stable (system)
2) runtime/com.github.Eloston.UngoogledChromium.Codecs/x86_64/stable (system)
3) All of the above

Which do you want to use (0 to abort)? [0-3]:}}

== Developers ==

* [https://docs.flatpak.org/en/latest/available-runtimes.html Flatpak - available runtimes]

These are all hosted on [https://flathub.org/ Flathub.org].

== Troubleshooting ==

=== Permission errors ===

If you receive errors about permissions then you may need to add your user to the '''flatpak''' group.

{{Note|You need to log out and log back in or reboot for the group change(s) to take effect}}

=== Fixing audio issues ===

If you have a minimal setup and don't have access to audio devices you will need to set the XDG_RUNTIME_DIR variable. Save the following script in {{Path|/etc/profile.d/xdg_runtime_dir.sh}} and re-login to have it set up properly.

if test -z "${XDG_RUNTIME_DIR}"; then
export XDG_RUNTIME_DIR=/tmp/$(id -u)
fi

When you launch a Flatpak you will need to start pulseaudio as well:

{{Cmd|$ pulseaudio --start && flatpak run com.example.Example}}

== Links ==
* [https://flatpak.org/ Flatpak]
* [https://flathub.org/ Flathub]
* [https://winepak.github.io/ Winepak]

[[Category:Package Manager]]
[[Category: Desktop]]

How to make a cross architecture chroot

2023-06-01T07:57:26Z

Bbbhltz: formatting, fixed broken link

If you have an ARM computer, you will find that some software is only available for x86_64. One possible solution is to have a full x86_64 virtual machine, but that has quite a lot of overhead from having to emulate the entire system. Fortunately, there is [https://qemu-project.gitlab.io/qemu/user/main.html QEMU User space emulation] which still uses the host kernel, so there is less overhead. This guide will show you how to make a chroot and enable transparent x86_64 binary execution using qemu and binfmt_misc.

== Prerequisites ==

You should be familiar with the Linux command line.

This guide is written assuming you have Alpine as the main install as well as putting Alpine in the chroot.

Also, the commands shown assume you have '''root''' privileges. Either use <code>sudo/doas</code> as needed (or <code>su</code> first).

== Installing necessary software ==

'''[[Repositories#Managing_repositories| Enable the Community Repository]]''' and install the '''qemu''' user mode binaries for the architectures you want to use, in this case x86_64 and i386:

{{Cmd|# apk add {{Pkg|qemu-x86_64}} {{Pkg|qemu-i386}}}}

Please note there are the <code>qemu-system-*</code> packages, you don't want those since they are used for full virtual machine emulation.

Then, <code>curl</code> my modified version of the qemu-binfmt script (originally from the [https://pkgs.alpinelinux.org/package/edge/community/aarch64/qemu-openrc qemu-openrc] package):

{{Cmd|# curl -o /etc/init.d/qemu-binfmt '<nowiki>https://gist.githubusercontent.com/ktprograms/c8ea850abde717376ff7a6f83dbabb2f/raw/0ff0596e8f9f1891f272393fa1ff0529bcbcef5d/qemu-binfmt</nowiki>'}}

I prefer to use this script instead of installing the {{Pkg|qemu-openrc}} package since that adds a lot of unneeded dependencies. Right now this only supports i386, x86_64, arm, ppc64le and s390x but I'll be adding all the architectures soon.

Make the qemu-binfmt script executable:

{{Cmd|# chmod +x /etc/init.d/qemu-binfmt}}

== Enable the <code>qemu-binfmt</code> service and start it ==

The qemu-binfmt script is an OpenRC init script that registers the binfmt_misc handlers when the service starts and unregisters them when the service stops. Add the service to the default runlevel and start it immediately:

{{Cmd|# rc-update add qemu-binfmt default
# rc-service qemu-binfmt start}}

== Make the chroot folder ==

To keep it simple, we're just going to use the apk repositories specified on the host system. This guide assumes the <code>$CHROOT</code> environment variable holds the directory where you want to make the chroot. Make the chroot directory and the <code>etc/apk</code> subdirectory (which we'll copy the apk repositories file to):

{{Cmd|# mkdir -p $CHROOT/etc/apk/}}

Now copy the host's apk repositories into the chroot folder:

{{Cmd|# cp /etc/apk/repositories $CHROOT/etc/apk/}}

You'll also need to copy the <code>resolv.conf</code> file into the chroot so it can have internet access:

{{Cmd|# cp /etc/resolv.conf $CHROOT/etc/}}

== Install <code>alpine-base</code> into the chroot folder ==

The {{Pkg|alpine-base}} meta package is all that's needed to have a fully working alpine system. The apk invocation used here has a few more options than what you might be used to:

{{Cmd|# apk add -p $CHROOT --initdb -U --arch x86_64 --allow-untrusted alpine-base}}

Here's what all the options do:

*<code>-p $CHROOT</code>: Sets the root of the install to <code>$CHROOT</code> instead of <code>/</code>
*<code>--initdb</code>: Initialize a new package database.
*<code>-U</code>: Alias for <code>--cache-max-age 1</code>. Basically means don't install from cache.
*<code>--arch x86_64</code>: Install x86_64 packages instead of native packages. Replace this with whichever architecture you want to emulate instead (e.g. <code>--arch x86</code>).
*<code>--allow-untrusted</code>: Install packages with untrusted signature or no signature. (This is needed since the keys for different architectures are different than what will be on your host. If you have the correct keys, you can copy them into the <code>$CHROOT/etc/apk/keys/</code> directory and remove this flag).

== Mount the virtual file systems into the chroot ==

{{Cmd|# mount -t proc proc $CHROOT/proc/
# mount -t sysfs sys $CHROOT/sys/
# mount -o bind /dev/ $CHROOT/dev/
# mount -o bind /dev/pts/ $CHROOT/dev/pts/
# mount -o bind /run $CHROOT/run/}}

==The exciting part: Enter the chroot==

If you've followed all the steps, this part should be uneventful. The <code>chroot</code> invocation uses the special command of <code>ash -l</code> to run as a login shell and source <code>/etc/profile</code>:

{{Cmd|# chroot $CHROOT/ ash -l}}

==Troubleshooting==

If you get a <code>ERROR: ${package_name}.post-install: script exited with error 127</code> while trying to add the alpine-base, that normally means that qemu binfmt_misc hasn't been setup properly. Check if the <code>qemu-$arch</code> package has been installed and see if the binfmt_misc service is running. You can also see if there is a <code>qemu-$arch</code> entry in <code>/proc/sys/fs/binfmt_misc/</code>.

Programs that use [https://en.wikipedia.org/wiki/Netlink Netlink] (e.g. <code>ip addr</code>) don't seem to work properly since qemu doesn't emulate the Netlink protocol properly.

==References==

* [https://archive.is/ldO0C Transparently running binaries from any architecture in Linux with QEMU and binfmt_misc] (see the section titled <code>Emulating full ARM rootfs</code>)

[[Category:System Administration]]

Damn Vulnerable Web Application (DVWA)

2023-05-30T20:26:39Z

Bbbhltz: formatting tweaks

For testing web security tools a target which has plenty vulnerabilities is needed. The [http://www.dvwa.co.uk Damn Vulnerable Web Application (DVWA)] provides a PHP/MySQL web application that is damn vulnerable.

== Install lighttpd, PHP, and MySql ==

{{:Setting Up Lighttpd With FastCGI}}

Install extra packages:

{{Cmd|# apk add php5-mysql mysql mysql-client}}

== Installing and configuring DVWA ==

Create the a folder named {{Path|webapps}}

{{Cmd|# mkdir -p /usr/share/webapps/}}

Download the source archive and unpack it:

{{Cmd|$ cd /usr/share/webapps/
# wget <nowiki>https://github.com/RandomStorm/DVWA/archive/v1.9.zip</nowiki>}}

Unpack the archive and remove it:

{{Cmd|# unzip v1.9.zip
# rm v1.9.zip}}

Change the folder permissions:

{{Cmd|# chmod -R 777 /usr/share/webapps/}}

Create a symlinks to the folder ''dvwa''

{{Cmd|# ln -s /usr/share/webapps/dvwa/ /var/www/localhost/htdocs/dvwa}}

== Configure and start MySql ==

{{Cmd|<nowiki># /usr/bin/mysql_install_db --user=mysql
# /etc/init.d/mariadb start && rc-update add mariadb default
# /usr/bin/mysqladmin -u root password 'password'</nowiki>}}

Modify the database credentials within DVWA configuration file {{Path|/config/config.inc.php}}

{{Cmd|# nano -w /usr/share/webapps/dvwa/config/config.inc.php}}

To complete the setup, browse to the DVWA directory on the webserver.

<nowiki>http://WEBSERVER_IP_ADDRESS/dvwa</nowiki>

Follow the link to setup the database.

[[Category:PHP]] [[Category:SQL]] [[Category:Security]]

Setting Up Lighttpd With FastCGI

2023-05-30T20:20:40Z

Bbbhltz: formatting and style tweaks, content unchanged

== Basic Installation ==

For installing the additional packages first '''[[Repositories#Managing_repositories|activate community packages]]''' and update the package index

Install the required packages:

{{Cmd|# apk add lighttpd php7-common php7-session php7-iconv php7-json php7-gd php7-curl php7-xml php7-mysqli php7-imap php7-cgi fcgi php7-pdo php7-pdo_mysql php7-soap php7-xmlrpc php7-posix php7-mcrypt php7-gettext php7-ldap php7-ctype php7-dom php7-simplexml}}

== Configure Lighttpd ==

Edit lighttpd.conf ({{Path|/etc/lighttpd/lighttpd.conf}}) and uncomment the line:

include "mod_fastcgi.conf"

== Start <code>lighttpd</code> service and add it to default runlevel ==

{{Cmd|# rc-service lighttpd start && rc-update add lighttpd default}}

[[Category:Server]]
[[Category:PHP]]

Talk:Installation

2023-05-30T10:46:25Z

Bbbhltz: /* New Discussions */ reply

== New Discussions ==

I wasn't here for most of the drama, but it might help with reducing redundant pages and poor verbiage if some of the other "install" pages were made subpages of this one. Instead of "Installing Alpine in a virtual machine", "Installing Alpine on VMware ESXi", "Alpine on ARM", etc... we could group by hypervisor (if any), then architecture or firmware, then board, etc... existing only where there are differences between others of the same level. For example:

* '''Installation/VirtualBox/BIOS''' -
* '''Installation/AARCH64/Raspberry Pi 4'''
* '''Installation/x86/Dell Inspiron 1525'''

Alternatively, we could duplicate the top level installation page for each architecture (like the Gentoo Handbook). That would allow better nuance in the initial media preparation and boot process. This page would then simply provide a brief guide of choosing the correct arch. [[User:Arrogance|Arrogance]] ([[User talk:Arrogance|talk]]) 09:17, 30 May 2023 (UTC)

:+1 for this idea. I'm not a pro at this but it would make it easier to navigate. Is the subpage feature on for regular pages? [[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 10:46, 30 May 2023 (UTC)

== Resolved Discussions==

=== Focused users and edits ===

We are aware that wiki is not so complete but, last month wiki installation page are a crap ton of changes.. The wiki page tries to include so many information.. but it lacks of good structure, neither hav a good requirements page

So then '''I separated the requirements detailed''' to a new wiki page, https://wiki.alpinelinux.org/wiki/Requirements, with all details and reduce significatively the installation page details to only RAM and SPACE storage..

Later added a section in https://wiki.alpinelinux.org/wiki/Alpine_newbie_install_manual#Ways_to_install_Alpine_listed_by_architectures so then '''users that need different methods of install does not need to crap''' with over information the only wiki installation page.. (over information) '''I mean over sentences of "for this ARM flafour go to here and here and for this toy go to here"'''

'''Last then i reduced rest of info to improved independent pages of each one!'''
Contributions must be focused in independent cases and listed in how to and tutorial wiki page .. so then i can check and later listed at new users tutorial pages.

All of this new pages will be improved in next days. Currently information was slpitted and improved to reduce the oversized installation page!

'''''About changes and recent diff from SB1 June and July changes..'''.''

'''Checksum command is a extra optional info''': first note are the checksum command to verify.. only takes in consideration linux (ovbiusly will be so "rare" if not) and win! there' is no more OS in the world? there's no MAC or FreeBSD? is clear Alpine need minimal linux knowledge so are nonsense try to catch win users without minimal linux knowledge.. specific pages for that must be done! not in main install pages!

'''Boot of external devices''' depends of each computer device so each wiki page cases of architecture installation must added its own information

'''also the use Sb1 erased/changed so many information''' and does not property posted in any other page .. (i mean setup alpine or similar) all the info was grouped and pasted in main installation page.. oversized the target of.. the good examples of wiki pages must be like: https://wiki.alpinelinux.org/wiki/Alpine_Linux:FAQ#What_is_the_difference_between_.27sys.27.2C_.27data.27.2C_and_.27diskless.27_when_running_.27setup-alpine.27_or_.27setup-disk.27.3F makes references to install page as further deep information available.. but this page as i said was changed significatively..

--[[User:mckaygerhard|mckaygerhard]] July 2020

* Sorry, it's problematic when your edits **replace** concise pages with your "alpine newbie" series style. (And that repeatedly.) For readers looking for information, these are a quite much convoluted agglomeration of multiple, unmaintainable pages with much overlapping and duplicate information and do not refrain from opinionated jargon. For example, it does not make much sense to move the recommended image verification commands into some [[Requirements]] page. That page is immense and convoluted with unmaintanable tables that for example only resemble statistics about the currently downloadable images. Further, parts of it are duplicated in the plethora of "Alpine_newbie" install recipes (in which readers that follow it or want to look up something to get lost in, without getting a much needed overview and information about the available options, to end up being able to arrive at well informed decisions). => So there are good reasons why your changes were reverted (12:40, 12 December 2020‎ "Reverting as of https://lists.alpinelinux.org/~alpine/devel/<20201002143513.yco7vwx2ci3lqezm@wolfsden.cz> Second time user Mckaygerhard pulled stunt on this page. (Aug.13/19 & Jul.12/20))

Template talk:Delete

2023-05-30T06:12:16Z

Bbbhltz: Reply

It might help admins to delete pages better (or others to fix the articles / contest their deletion) if this template included a category. <nowiki><includeonly>[[Category:Articles for deletion]]</includeonly></nowiki>, for example. I'd add it myself, but for some reason it's been made admin-only.[[User:Arrogance|Arrogance]] ([[User talk:Arrogance|talk]]) 04:04, 30 May 2023 (UTC)

: Like this? https://wiki.alpinelinux.org/wiki/Special:WhatLinksHere/Template:Delete [[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 05:25, 30 May 2023 (UTC)
::No. Lots of pages can potentially link to a template without using it, or needing to be deleted. It also makes it easier to parse with tools. [[User:Arrogance|Arrogance]] ([[User talk:Arrogance|talk]]) 06:03, 30 May 2023 (UTC)
:::OK. I just understood what you meant. [[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 06:12, 30 May 2023 (UTC)

Template talk:Delete

2023-05-30T05:25:47Z

Bbbhltz: Reply to Arrogance

Category:Web Browser

2023-05-29T19:27:11Z

Bbbhltz: added Tor

A web browser is an application for accessing websites. When a user requests a web page from a particular website, the browser retrieves its files from a web server and then displays the page on the user’s screen.

Alpine Linux packages several web browsers.

== Console ==

* '''Elinks''' {{Pkg|elinks}}: feature-rich text mode web browser
* '''Links''' {{Pkg|links}}/{{Pkg|links-graphics}}: web browser with both graphics and text mode
* '''Lynx''' {{Pkg|lynx}}: text-based browser
* '''w3m''' {{Pkg|w3m}}: text-based web & gopher browser, as well as pager

== Graphical ==

* '''Badwolf''' {{Pkg|badwolf}}: A minimalist and privacy-oriented WebKit browser
* '''Chromium''' {{Pkg|chromium}}: the open source project behind Google Chrome, Blink-based
* '''Dillo''' {{Pkg|dillo}}: small and fast GUI web browser
* '''Epiphany/GNOME Web''' {{Pkg|epiphany}}: GNOME's WebKitGTK-based browser
* '''[[Firefox]]''': browser from Mozilla based on Gecko with fast rendering
* '''Midori''' {{Pkg|midori}}: web browser based on GTK and WebKit
* '''Netsurf''' {{Pkg|netsurf}}: an open source web browser
* '''Nyxt''' {{Pkg|nyxt}}: the ''“hacker’s browser”''
* '''Qutebrowser''' {{Pkg|qutebrowser}}: keyboard-driven, Vim-like browser based on PyQT5
* '''Surf''' {{Pkg|surf}}: a simple web browser based on WebKit2/GTK+
* '''Tor''' {{Pkg|tor}}: a modified Mozilla Firefox ESR web browser used for accessing the Tor network — usually not recommended for general web browsing
* '''Vieb''' {{Pkg|vieb}}: Vim-inspired Electron browser
* '''Vimb''' {{Pkg|vimb}}: a Vim-like browser

[[category: Desktop]]

Category:Web Browser

2023-05-29T19:22:16Z

Bbbhltz: had an epiphany

A web browser is an application for accessing websites. When a user requests a web page from a particular website, the browser retrieves its files from a web server and then displays the page on the user’s screen.

Alpine Linux packages several web browsers.

== Console ==

* '''Elinks''' {{Pkg|elinks}}: feature-rich text mode web browser
* '''Links''' {{Pkg|links}}/{{Pkg|links-graphics}}: web browser with both graphics and text mode
* '''Lynx''' {{Pkg|lynx}}: text-based browser
* '''w3m''' {{Pkg|w3m}}: text-based web & gopher browser, as well as pager

== Graphical ==

* '''Badwolf''' {{Pkg|badwolf}}: A minimalist and privacy-oriented WebKit browser
* '''Chromium''' {{Pkg|chromium}}: the open source project behind Google Chrome, Blink-based
* '''Dillo''' {{Pkg|dillo}}: small and fast GUI web browser
* '''Epiphany/GNOME Web''' {{Pkg|epiphany}}: GNOME's WebKitGTK-based browser
* '''[[Firefox]]''': browser from Mozilla based on Gecko with fast rendering
* '''Midori''' {{Pkg|midori}}: web browser based on GTK and WebKit
* '''Netsurf''' {{Pkg|netsurf}}: an open source web browser
* '''Nyxt''' {{Pkg|nyxt}}: the ''“hacker’s browser”''
* '''Qutebrowser''' {{Pkg|qutebrowser}}: keyboard-driven, Vim-like browser based on PyQT5
* '''Surf''' {{Pkg|surf}}: a simple web browser based on WebKit2/GTK+
* '''Vieb''' {{Pkg|vieb}}: Vim-inspired Electron browser
* '''Vimb''' {{Pkg|vimb}}: a Vim-like browser

[[category: Desktop]]

Category:Web Browser

2023-05-29T19:13:58Z

Bbbhltz: added list to category page to help new users discover which browsers are available in Alpine

A web browser is an application for accessing websites. When a user requests a web page from a particular website, the browser retrieves its files from a web server and then displays the page on the user’s screen.

Alpine Linux packages several web browsers.

== Console ==

* '''Elinks''' {{Pkg|elinks}}: feature-rich text mode web browser
* '''Links''' {{Pkg|links}}/{{Pkg|links-graphics}}: web browser with both graphics and text mode
* '''Lynx''' {{Pkg|lynx}}: text-based browser
* '''w3m''' {{Pkg|w3m}}: text-based web & gopher browser, as well as pager

== Graphical ==

* '''Badwolf''' {{Pkg|badwolf}}: A minimalist and privacy-oriented WebKit browser
* '''Chromium''' {{Pkg|chromium}}: the open source project behind Google Chrome, Blink-based
* '''Dillo''' {{Pkg|dillo}}: small and fast GUI web browser
* '''[[Firefox]]''': browser from Mozilla based on Gecko with fast rendering
* '''Midori''' {{Pkg|midori}}: web browser based on GTK and WebKit
* '''Netsurf''' {{Pkg|netsurf}}: an open source web browser
* '''Nyxt''' {{Pkg|nyxt}}: the ''“hacker’s browser”''
* '''Qutebrowser''' {{Pkg|qutebrowser}}: keyboard-driven, Vim-like browser based on PyQT5
* '''Surf''' {{Pkg|surf}}: a simple web browser based on WebKit2/GTK+
* '''Vieb''' {{Pkg|vieb}}: Vim-inspired Electron browser
* '''Vimb''' {{Pkg|vimb}}: a Vim-like browser

[[category: Desktop]]

Firefox

2023-05-29T19:01:33Z

Bbbhltz: minor formatting/style

Firefox is a popular, open-source [https://en.wikipedia.org/wiki/Web_browser web browser].

== Installation ==

To install Firefox, firstly enable the [[Repositories#Enabling_the_community_repository|Community repository]], then type in the terminal:

For the Extended Support Release (ESR) ({{Pkg|firefox-esr}}):

{{Cmd|# apk add firefox-esr}}

For the current release ({{Pkg|firefox}}):

{{Cmd|# apk add firefox}}

== Stability ==

If [https://support.mozilla.org/en-US/questions/1175046 tabs crash], then try disabling hardware acceleration, in the Preferences - Performance menu.

== Notifications ==

For Firefox to use native notifications (e.g.: via a notification daemon) the {{Pkg|libnotify}} package is required.

== See Also ==

* [https://git.alpinelinux.org/aports/log/?id=05e5fbf809000e016eee3fdfdaffb6e39a4956fd&qt=grep&q=firefox Git repositories for Alpine Linux]
* [https://stackoverflow.com/questions/51806403/installation-of-firefox-from-alpine-edge Installation of Firefox from Alpine Edge]

[[category: Web Browser]]

K8s

2023-05-26T21:03:31Z

Bbbhltz: added category

= Alpine Linux 🌲 K8s in 10 Minutes =

== Summary ==

This guide will allow you to deploy a fresh Alpine Linux install into a Kubernetes K8 cluster in less than 10 minutes.

== Why ✨ ==

I went to learn Kubernetes recently and I built a k3 cluster using Alpine in an hour or so, it was a great experience. I figured the next step would be K8s, but I found no material on K8s for Alpine. This guide is the result of my first pass and the incorporations of high quality notes from the contributers. Kubernetes 🦄 is awesome.

== Contributers ==

* Matthew Rogers [https://github.com/RamboRogers Github] [https://www.linkedin.com/in/matthewrogerscissp/ LinkedIn]
* Mike Zolla [https://github.com/Zolla-Zolla Github] [https://www.linkedin.com/in/mike-zolla-5903b8/ LinkedIn]
* Matthew Emmett [https://github.com/mattemmett Github] [https://www.linkedin.com/in/mattemmett/ LinkedIn]

-----

= Build K8s on Alpine Linux 🌲 =

=== Prerequisites 🔍 ===

You need an [https://alpinelinux.org/ Alpine Linux] install (this guide is written against version 3.17 standard image) with internet access. I recommend at least 2 CPU with 4GB of ram and 10GB of disk for each node.

<blockquote>For HA control planes you'll need a mininum of three nodes
</blockquote>

=== 1. Setup the Repositories 📗 ===

Update you repositories under {{Path|/etc/apk/repositories}} to include '''community''', '''edge community''' and '''testing'''.

{{Cat|/etc/apk/repositories|#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.17/main
http://dl-cdn.alpinelinux.org/alpine/v3.17/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing}}

=== 2. Node Setup 🖥️ ===

This series of commands solves a series is incremental problems and sets up the system (if the first control node) for kubectl/kubeadm to run properly on next login by linking the config.

The result here gives you a functional node that can be joined to an existing cluster or can become the first control plane of a new cluster. 🎶

{{Note|🔔 This build assumes CNI usage of flannel for networking 🔔}}

'''Add kernel module for networking stuff'''

{{Cmd|# echo "br_netfilter" > /etc/modules-load.d/k8s.conf
# modprobe br_netfilter
# echo 1 > /proc/sys/net/ipv4/ip_forward
# apk add {{Pkg|cni-plugin-flannel}}
# apk add {{Pkg|cni-plugins}}
# apk add {{Pkg|flannel}}
# apk add {{Pkg|flannel-contrib-cni}}
# apk add {{Pkg|kubelet}}
# apk add {{Pkg|kubeadm}}
# apk add {{Pkg|kubectl}}
# apk add {{Pkg|containerd}}
# apk add {{Pkg|uuidgen}}
# apk add {{Pkg|nfs-utils}}}}

'''Get rid of swap'''

{{Cmd|# cat /etc/fstab | grep -v swap > temp.fstab
# cat temp.fstab > /etc/fstab
# rm temp.fstab
# swapoff -a}}

'''Fix prometheus errors'''

{{Cmd|# mount --make-rshared /
# echo "#!/bin/sh" > /etc/local.d/sharemetrics.start
# echo "mount --make-rshared /" >> /etc/local.d/sharemetrics.start
# chmod +x /etc/local.d/sharemetrics.start
# rc-update add local}}

'''Fix id error messages'''

{{Cmd|# uuidgen > /etc/machine-id}}

'''Add services'''

{{Cmd|# rc-update add containerd
# rc-update add kubelet}}

'''Sync time'''

{{Cmd|# rc-update add ntpd
# /etc/init.d/ntpd start
# /etc/init.d/containerd start}}

'''Fix flannel'''

{{Cmd|# ln -s /usr/libexec/cni/flannel-amd64 /usr/libexec/cni/flannel}}

'''Kernel stuff'''

{{Cmd|# echo "net.bridge.bridge-nf-call-iptables{{=}}1" >> /etc/sysctl.conf
# sysctl net.bridge.bridge-nf-call-iptables{{=}}1}}

'''Pin your versions!''' If you update and the nodes get out of sync, it implodes.

{{Cmd|# apk add 'kubelet{{=}}~1.26'
# apk add 'kubeadm{{=}}~1.26'
# apk add 'kubectl{{=}}~1.26'}}

{{Note|In the future you will manually have to add a newer version the same way to upgrade.}}

Your blank node is now ready! If it's the first, you'll want to make a control node.

=== 3. Setup the Control Plane (New Cluster!) 🦾 ===

Run this command to start the cluster and then apply a network.

<pre>
#do not change subnet
kubeadm init --pod-network-cidr=10.244.0.0/16 --node-name=$(hostname)
mkdir ~/.kube
ln -s /etc/kubernetes/admin.conf /root/.kube/config
kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
</pre>
You now have a control plane. This also gives you the command to run on our blank nodes to add them to this cluster as workers.

=== 4. Join the cluster. 🐜 ===

Run this to get the join command from the control plane which you would then run on your new worker.
<pre>
kubeadm token create --print-join-command
</pre>

= Bonus 💰 =

== Setup NFS Mounts on K8s ==

This can be shared NFS storage to allow for auto persistent claim fulfilment. You'll need your IP updated and export information.

<pre>helm repo add nfs-subdir-external-provisioner https://kubernetes-sigs.github.io/nfs-subdir-external-provisioner/
helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \
--set nfs.server=192.168.1.31 \
--set nfs.path=/exports/cluster00
</pre>
Now set the default storage class for the cluster.

<pre>kubectl get storageclass
kubectl patch storageclass nfs-client -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
</pre>
== Check on System 👀 ==

Check on your system.

<pre>kubectl get nodes
kubectl get all
</pre>

[[Category:Virtualization]]

K8s

2023-05-26T21:02:43Z

Bbbhltz: /* 1. Setup the Repositories 📗 */ formatting

K8s

2023-05-26T21:01:25Z

Bbbhltz: /* 2. Node Setup 🖥️ */ formatting

= Alpine Linux 🌲 K8s in 10 Minutes =

== Summary ==

This guide will allow you to deploy a fresh Alpine Linux install into a Kubernetes K8 cluster in less than 10 minutes.

== Why ✨ ==

I went to learn Kubernetes recently and I built a k3 cluster using Alpine in an hour or so, it was a great experience. I figured the next step would be K8s, but I found no material on K8s for Alpine. This guide is the result of my first pass and the incorporations of high quality notes from the contributers. Kubernetes 🦄 is awesome.

== Contributers ==

* Matthew Rogers [https://github.com/RamboRogers Github] [https://www.linkedin.com/in/matthewrogerscissp/ LinkedIn]
* Mike Zolla [https://github.com/Zolla-Zolla Github] [https://www.linkedin.com/in/mike-zolla-5903b8/ LinkedIn]
* Matthew Emmett [https://github.com/mattemmett Github] [https://www.linkedin.com/in/mattemmett/ LinkedIn]

-----

= Build K8s on Alpine Linux 🌲 =

=== Prerequisites 🔍 ===

You need an [https://alpinelinux.org/ Alpine Linux] install (this guide is written against version 3.17 standard image) with internet access. I recommend at least 2 CPU with 4GB of ram and 10GB of disk for each node.

<blockquote>For HA control planes you'll need a mininum of three nodes
</blockquote>

=== 1. Setup the Repositories 📗 ===

Update you repositories under /etc/apk/repositories to include community, edge community and testing.

<pre>#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.17/main
http://dl-cdn.alpinelinux.org/alpine/v3.17/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing
</pre>
=== 2. Node Setup 🖥️ ===

This series of commands solves a series is incremental problems and sets up the system (if the first control node) for kubectl/kubeadm to run properly on next login by linking the config.

The result here gives you a functional node that can be joined to an existing cluster or can become the first control plane of a new cluster. 🎶

{{Note|🔔 This build assumes CNI usage of flannel for networking 🔔}}

'''Add kernel module for networking stuff'''

{{Cmd|# echo "br_netfilter" > /etc/modules-load.d/k8s.conf
# modprobe br_netfilter
# echo 1 > /proc/sys/net/ipv4/ip_forward
# apk add {{Pkg|cni-plugin-flannel}}
# apk add {{Pkg|cni-plugins}}
# apk add {{Pkg|flannel}}
# apk add {{Pkg|flannel-contrib-cni}}
# apk add {{Pkg|kubelet}}
# apk add {{Pkg|kubeadm}}
# apk add {{Pkg|kubectl}}
# apk add {{Pkg|containerd}}
# apk add {{Pkg|uuidgen}}
# apk add {{Pkg|nfs-utils}}}}

'''Get rid of swap'''

{{Cmd|# cat /etc/fstab | grep -v swap > temp.fstab
# cat temp.fstab > /etc/fstab
# rm temp.fstab
# swapoff -a}}

'''Fix prometheus errors'''

{{Cmd|# mount --make-rshared /
# echo "#!/bin/sh" > /etc/local.d/sharemetrics.start
# echo "mount --make-rshared /" >> /etc/local.d/sharemetrics.start
# chmod +x /etc/local.d/sharemetrics.start
# rc-update add local}}

'''Fix id error messages'''

{{Cmd|# uuidgen > /etc/machine-id}}

'''Add services'''

{{Cmd|# rc-update add containerd
# rc-update add kubelet}}

'''Sync time'''

{{Cmd|# rc-update add ntpd
# /etc/init.d/ntpd start
# /etc/init.d/containerd start}}

'''Fix flannel'''

{{Cmd|# ln -s /usr/libexec/cni/flannel-amd64 /usr/libexec/cni/flannel}}

'''Kernel stuff'''

{{Cmd|# echo "net.bridge.bridge-nf-call-iptables{{=}}1" >> /etc/sysctl.conf
# sysctl net.bridge.bridge-nf-call-iptables{{=}}1}}

'''Pin your versions!''' If you update and the nodes get out of sync, it implodes.

{{Cmd|# apk add 'kubelet{{=}}~1.26'
# apk add 'kubeadm{{=}}~1.26'
# apk add 'kubectl{{=}}~1.26'}}

{{Note|In the future you will manually have to add a newer version the same way to upgrade.}}

Your blank node is now ready! If it's the first, you'll want to make a control node.

=== 3. Setup the Control Plane (New Cluster!) 🦾 ===

Run this command to start the cluster and then apply a network.

<pre>
#do not change subnet
kubeadm init --pod-network-cidr=10.244.0.0/16 --node-name=$(hostname)
mkdir ~/.kube
ln -s /etc/kubernetes/admin.conf /root/.kube/config
kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
</pre>
You now have a control plane. This also gives you the command to run on our blank nodes to add them to this cluster as workers.

=== 4. Join the cluster. 🐜 ===

Run this to get the join command from the control plane which you would then run on your new worker.
<pre>
kubeadm token create --print-join-command
</pre>

= Bonus 💰 =

== Setup NFS Mounts on K8s ==

This can be shared NFS storage to allow for auto persistent claim fulfilment. You'll need your IP updated and export information.

<pre>helm repo add nfs-subdir-external-provisioner https://kubernetes-sigs.github.io/nfs-subdir-external-provisioner/
helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \
--set nfs.server=192.168.1.31 \
--set nfs.path=/exports/cluster00
</pre>
Now set the default storage class for the cluster.

<pre>kubectl get storageclass
kubectl patch storageclass nfs-client -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
</pre>
== Check on System 👀 ==

Check on your system.

<pre>kubectl get nodes
kubectl get all
</pre>

K8s

2023-05-26T20:50:30Z

Bbbhltz: /* Prerequisits 🔍 */ typo

= Alpine Linux 🌲 K8s in 10 Minutes =

== Summary ==

This guide will allow you to deploy a fresh Alpine Linux install into a Kubernetes K8 cluster in less than 10 minutes.

== Why ✨ ==

I went to learn Kubernetes recently and I built a k3 cluster using Alpine in an hour or so, it was a great experience. I figured the next step would be K8s, but I found no material on K8s for Alpine. This guide is the result of my first pass and the incorporations of high quality notes from the contributers. Kubernetes 🦄 is awesome.

== Contributers ==

* Matthew Rogers [https://github.com/RamboRogers Github] [https://www.linkedin.com/in/matthewrogerscissp/ LinkedIn]
* Mike Zolla [https://github.com/Zolla-Zolla Github] [https://www.linkedin.com/in/mike-zolla-5903b8/ LinkedIn]
* Matthew Emmett [https://github.com/mattemmett Github] [https://www.linkedin.com/in/mattemmett/ LinkedIn]

-----

= Build K8s on Alpine Linux 🌲 =

=== Prerequisites 🔍 ===

You need an [https://alpinelinux.org/ Alpine Linux] install (this guide is written against version 3.17 standard image) with internet access. I recommend at least 2 CPU with 4GB of ram and 10GB of disk for each node.

<blockquote>For HA control planes you'll need a mininum of three nodes
</blockquote>

=== 1. Setup the Repositories 📗 ===

Update you repositories under /etc/apk/repositories to include community, edge community and testing.

<pre>#/media/cdrom/apks
http://dl-cdn.alpinelinux.org/alpine/v3.17/main
http://dl-cdn.alpinelinux.org/alpine/v3.17/community
#http://dl-cdn.alpinelinux.org/alpine/edge/main
http://dl-cdn.alpinelinux.org/alpine/edge/community
http://dl-cdn.alpinelinux.org/alpine/edge/testing
</pre>
=== 2. Node Setup 🖥️ ===

This series of commands solves a series is incremental problems and sets up the system (if the first control node) for kubectl/kubeadm to run properly on next login by linking the config.

The result here gives you a functional node that can be joined to an existing cluster or can become the first control plane of a new cluster. 🎶

<blockquote>*** 🔔 This build assumes CNI usage of flannel for networking 🔔 ***
</blockquote>
<pre>#add kernel module for networking stuff
echo "br_netfilter" > /etc/modules-load.d/k8s.conf
modprobe br_netfilter
echo 1 > /proc/sys/net/ipv4/ip_forward
apk add cni-plugin-flannel
apk add cni-plugins
apk add flannel
apk add flannel-contrib-cni
apk add kubelet
apk add kubeadm
apk add kubectl
apk add containerd
apk add uuidgen
apk add nfs-utils
#get rid of swap
cat /etc/fstab | grep -v swap > temp.fstab
cat temp.fstab > /etc/fstab
rm temp.fstab
swapoff -a
#Fix prometheus errors
mount --make-rshared /
echo "#!/bin/sh" > /etc/local.d/sharemetrics.start
echo "mount --make-rshared /" >> /etc/local.d/sharemetrics.start
chmod +x /etc/local.d/sharemetrics.start
rc-update add local
#Fix id error messages
uuidgen > /etc/machine-id
#Add services
rc-update add containerd
rc-update add kubelet
#Sync time
rc-update add ntpd
/etc/init.d/ntpd start
/etc/init.d/containerd start
#fix flannel
ln -s /usr/libexec/cni/flannel-amd64 /usr/libexec/cni/flannel
#kernel stuff
echo "net.bridge.bridge-nf-call-iptables=1" >> /etc/sysctl.conf
sysctl net.bridge.bridge-nf-call-iptables=1
#Pin your versions! If you update and the nodes get out of sync, it implodes.
apk add 'kubelet=~1.26'
apk add 'kubeadm=~1.26'
apk add 'kubectl=~1.26'
#Note that in the future you will manually have to add a newer version the same way to upgrade.
</pre>
Your blank node is now ready! If it's the first, you'll want to make a control node.

=== 3. Setup the Control Plane (New Cluster!) 🦾 ===

Run this command to start the cluster and then apply a network.

<pre>
#do not change subnet
kubeadm init --pod-network-cidr=10.244.0.0/16 --node-name=$(hostname)
mkdir ~/.kube
ln -s /etc/kubernetes/admin.conf /root/.kube/config
kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
</pre>
You now have a control plane. This also gives you the command to run on our blank nodes to add them to this cluster as workers.

=== 4. Join the cluster. 🐜 ===

Run this to get the join command from the control plane which you would then run on your new worker.
<pre>
kubeadm token create --print-join-command
</pre>

= Bonus 💰 =

== Setup NFS Mounts on K8s ==

This can be shared NFS storage to allow for auto persistent claim fulfilment. You'll need your IP updated and export information.

<pre>helm repo add nfs-subdir-external-provisioner https://kubernetes-sigs.github.io/nfs-subdir-external-provisioner/
helm install nfs-subdir-external-provisioner nfs-subdir-external-provisioner/nfs-subdir-external-provisioner \
--set nfs.server=192.168.1.31 \
--set nfs.path=/exports/cluster00
</pre>
Now set the default storage class for the cluster.

<pre>kubectl get storageclass
kubectl patch storageclass nfs-client -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
</pre>
== Check on System 👀 ==

Check on your system.

<pre>kubectl get nodes
kubectl get all
</pre>

How to run Spice Agent

2023-05-26T20:43:44Z

Bbbhltz: added category

=How To Run Spice Agent in Alpine=

This is a guide on how to run Spice Agent in Alpine Linux 3.12.1-standard.

The Spice Agent can be used to get some additional features when running Alpine Linux in a Qemu/Libvirt VM.

=Features=
Working:
* Client mouse mode
* Automatic adjustment of the X-session resolution
* Clipboard sharing

Not working:
* The <code>State</code> field in Libvirt - it always shows "disconnected", even when it is working

Not tested:
* Transferring files
* Multiple displays/screens

=Before You Start=
Most features of the Spice Agent are only useful when running a graphical interface.
I roughly followed the [[AwesomeWM]] guide, but substituted <code>awesome</code> with <code>i3wm</code> as that has my preference (you have to install {{Pkg|i3status}} manually, and use <code>i3</code> in the <code>.xinitrc</code> file).

For the Spice Agent to work, don't remove the <code>Channel spice</code> that is automatically added by Libvirt.

=Building the Spice Agent=
Install the dependencies:
# apk add alpine-sdk autoconf automake glib-dev libxfixes-dev libxrandr-dev libxinerama-dev spice-protocol alsa-lib-dev dbus-dev libdrm-dev libpciaccess-dev

Get the source code:
$ git clone https://gitlab.freedesktop.org/spice/linux/vd_agent.git
$ cd vd_agent
$ git checkout spice-vdagent-0.20.0
We need this specific version because the newest version requires a newer <code>spice-protocol</code> version than is provided by the repositories (version 0.14.1). If you follow this guide with a later version of Alpine, you may want to get a newer version from git as well.

Build the code (still in the {{Path|vd_agent}} directory):
$ ./autogen.sh
$ make

Install the program (should be optional when running manually, but I haven't tried it without yet):
# make install

=Running the Spice Agent=

==Running manually==
First start the <code>spice-vdagentd</code>:
# modprobe uinput
# mkdir /run/spice-vdagentd
# spice-vdagentd -d -x -X
You can also remove the lower-case <code>-x</code> flag to deamonize the <code>spice-vdagentd</code>.

Then start the <code>spice-vdagent</code>:
$ spice-vdagent -x -d
Notice that there is no need to run this last command as root.

==Running with init script==
''This assumes you ran <code>make install</code> at the end of building. If you have not, you'll have to change this accordingly. It also requires that <code>uinput</code> can be loaded with <code>modprobe</code>. If you cannot, look at [[#Using_the_virt_edition_of_Alpine]].''

To run with an init script, we will use the Gentoo init script, although we have to change the paths to make it work properly (latest commit is <code>b3b3e1d9a13c389f17e01c78c6c1a996d08420b5</code> at the time of writing):
$ wget https://gitweb.gentoo.org/repo/gentoo.git/plain/app-emulation/spice-vdagent/files/spice-vdagent.initd-4
$ sed 's,/var/run,/run,g;s,/usr/sbin,/usr/local/sbin,g' spice-vdagent.initd-4 > spice-vdagentd
Then we move the file to the right location, change the ownership, make it executable and add it to the default runlevel:
# mv spice-vdagentd /etc/init.d/
# chown root:root /etc/init.d/spice-vdagentd
# chmod +x /etc/init.d/spice-vdagentd
# rc-update add spice-vdagentd default

The above will start the <code>spice-vdagentd</code>, but not the <code>spice-vdagent</code>. As the <code>spice-vdagent</code> should be started with the de/wm you're using, there is not one general way which works for all setups. If you want to find a way that works for you, [https://wiki.archlinux.org/index.php/Autostarting#On_desktop_environment_startup the Arch wiki has a decent page on autostarting].

=Using the virt edition of Alpine=
This currently does not work on the virt edition (version 3.12.1), as it doesn't have <code>uinput</code> enabled in the kernel. However, there are still several ways to get it working.

==Run without uinput==
You can make the <code>spice-vdagentd</code> work without the uinput module by starting it as follows, but it will disable the cursor while the <code>spice-vdagent</code> is running:
# mkdir /run/spice-vdagentd
# spice-vdagentd -d -x -X -u /dev/null -f

==Build uinput as module==
{{Draft|The following contains all necessary information, but has to be rewritten to be more clear.}}
Follow the steps in [[Creating_an_Alpine_package#Setup_your_system_and_account|Setup your system and account for building packages]] and cd to the {{Path|aports/main/linux-lts}} directory.
Check that the kernel version you've pulled is the same that you're running with <code>uname -r</code> and <code>head APKBUILD</code>.
If they mismatch, checkout the aports branch that has the same kernel version.
If they are the same, continue with the following steps:
$ abuild deps
$ abuild fetch verify
$ abuild unpack
$ abuild prepare
$ cd src/build-virt-x86_64
Now change <code>CONFIG_INPUT_UINPUT</code> from not being included to <code>CONFIG_INPUT_UINPUT=m</code> in the <code>.config</code> file. Then proceed as follows:
$ make modules_prepare
$ make drivers/input/misc/uinput.ko
This builds the <code>uinput</code> module in the current directory. Every time you want to use it, you'll have to load it like this (still from {{Path|aports/main/linux-lts/src/build-virt-x86_64}}):
# insmod drivers/input/misc/uinput.ko
After this, you can use the spice agent as described in [[How_to_run_Spice_Agent#Running_the_Spice_Agent|Running the Spice Agent]], except that the <code>modprobe uinput</code> is not necessary.

Alternatively, you can "install" the module by copying it to {{Path|/lib/modules/`uname -r`/extra}} (which you'll most likely have to create first) and running <code>depmod</code> (as root).
After this, you can load the module normally with <code>modprobe uinput</code>.
This is necessary if you want to use the init script as described in [[#Running_with_init_script]].

==Rebuild the kernel to include uinput==
See [[Custom_Kernel]] for pointers on how to build a custom kernel. The option you'll need to change in the config is <code>CONFIG_INPUT_UINPUT</code>.

[[Category:Virtualization]]

Awesome(wm) Setup

2023-05-26T20:40:37Z

Bbbhltz:

#REDIRECT [[AwesomeWM]]

{{Delete|Empty page, just a redirect}}

How to run Spice Agent

2023-05-26T20:39:05Z

Bbbhltz: /* Before You Start */ update link to page instead of redirect, minor formatting

Awesome

2023-05-26T20:36:28Z

Bbbhltz:

#REDIRECT [[AwesomeWM]]

{{Delete|just a redirect}}

Setting up Transmission (bittorrent) with Clutch WebUI

2023-05-26T20:31:15Z

Bbbhltz: formatting and typos

== Introduction ==

This document will show you how you can setup [https://transmissionbt.com/ Transmission BitTorrent] client on Alpine Linux and control it with a nice HTTP web-interface. It is assumed that you know the basics of Alpine Linux (package management and internals) and you have enough storage available for your downloaded media (i.e. USB hard drive) and, of course, a working internet connection.

== Setting up Transmission ==

Lets install it:

{{Cmd|# apk add {{Pkg|transmission-daemon}}}}

This should install latest available version of Transmission (available on Alpine). After the installation is complete you should have default configuration file for init in {{Path|/etc/conf.d/transmission-daemon}}.

By default, Transmission will run as the user '''transmission'''. If you need to make changes, do so, and save them. You can restart <code>transmission-daemon</code> and see if all is working as desired:

{{Cmd|# rc-service transmission-daemon restart}}

To configure the transmission settings (including the download location), edit the configuration file here: {{Path|/var/lib/transmission/config/settings.json}}

If everything is working, you should see <code>transmission-daemon</code> running with the following command:

{{Cmd|$ ps}}

If you change the download location in the settings, remember to transfer ownership to the '''transmission''' user and group.

{{Cmd|# chown -R transmission:transmission <DOWNLOAD_FOLDER>}}

It may also be convenient for the '''root''' user to be able to access the files when administering the server. An easy way to do this is to add the root user to the '''transmission''' group:

{{Cmd|# addgroup root transmission}}

Let's add <code>transmission</code> to our system start:

{{Cmd|# rc-update add transmission-daemon}}

The transmission web GUI will run on <code>http://<IP_ADDRESS>:9091/transmission</code>

== Saving your changes to disk ==

Now is a good time to write your changes to disk:

{{Cmd|# lbu_commit device}}

[[Category:Server]]

User talk:Sb1

2023-05-23T07:33:47Z

Bbbhltz: sig

Hi,
I noticed your recent edits to Installation page made quite a development on an optional matter ('''headless config'''), that may still be of interest for many. 
I can see a few downsides on how it stands now:
* instructions for an ''optional thing'' are becoming very long (and yet incomplete)
* described method requires quite some familiarity with Alpine, whereas this guide is intended for new comers
* that solution has several pitfalls (it will transfer all same settings to any server installed with said apkovl, etc...)

I'm not sure why a reference to a straightforward and working third-party solution is now removed from wiki. 
Wiki is not official doc, and any mention does not express endorsement: quality external references are just fine in wiki. Referring to ''backdoor'' is irrelevant on this topic: it is not a good place to state personal judgement. 
As for the longer option you describe, it may fit better into tutorial section where things could be detailed more.

Would you reconsider the edits in that part?

:We could add the link (https://github.com/macmpi/alpine-linux-headless-bootstrap) to the main [[Raspberry Pi]] page. [[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 15:18, 20 May 2023 (UTC)

::That third-party apkovl solution works on any Alpine platform it is not limited to Pi-thing: I've been successfully using it on x86_64, x86,... So referring to it from main install page makes sense --[[User:Alpwik|Alpwik]] ([[User talk:Alpwik|talk]]) 15:07, 21 May 2023 (UTC)

* That headless.apkovl has too many security complaints filed, and unfortunately the author has not yet chosen to take the secure-defaults-first approach. The overlay makes users accept publicly shipped "private"(not) keys, by default, and continues starting that unsecured sshd root login server after an installation, by default. Obviously wrong things, but the issues that got filed are hidden as "closed" without actually fixing the wrong behavior. That was the reason for the link removal, to not have users directed to it, at least not without prominent warning. At the moment, sadly, instead of fixing the defaults, the github readme actually kind of hides the facts in in descriptive footnotes that do not mention the consequences. --[[User:Sb1|Sb1]]
: Ok, noted you are not happy with that solution, it's your own opinion. Please consider there are many different opinions out there (repo stars appreciations give some clues; you can discuss the topic there, etc...). This '''wiki is not a place for advocacy''', revenge statement or frustration expression: this does not help users and make things very confusing. Please consider reverting your last changes. --[[User:Alpwik|Alpwik]] ([[User talk:Alpwik|talk]]) 06:23, 23 May 2023 (UTC)

:: Sorry both of you. It appears that I made a change on the page by accident. My son touched the keyboard when I wasn't looking. Please feel free to "undo" whatever I just change on the Installation page. [[User:Bbbhltz|bbbhltz]] ([[User talk:Bbbhltz|talk]]) 07:33, 23 May 2023 (UTC)

User talk:Sb1

2023-05-23T07:33:32Z

Bbbhltz: mea culpa