Alpine Linux - User contributions [en]

Eudev

2025-08-17T18:43:11Z

Espindola: /* Manual installation */

{{DISPLAYTITLE:eudev}}
[https://github.com/eudev-project/eudev eudev] is a [[Device_Manager|device manager]] that provides a drop-in replacement for systemd udev. It is therefore recommended for full blown desktop environments.

== Installation ==

The easy way to setup eudev is through the [[#Setup_script|setup script]]. Only advanced users are recommended to do [[#Manual installation|manual installation]].

=== Setup script ===
{{:Include:Setup Device Manager}}

=== Manual installation ===

You need to install eudev itself and the udev services. {{cmd|# apk add {{pkg|eudev}} {{pkg|udev-init-scripts}}}}

If you already have a device manager installed you need to stop it before you start eudev. Then enable the following services.
{{cmd|<nowiki># rc-update add udev sysinit
# rc-update add udev-trigger sysinit
# rc-update add udev-settle sysinit
# rc-update add udev-postmount default
</nowiki>}}

If you are not running in a chroot you will also want to start eudev. {{cmd|<nowiki># rc-service udev start
# rc-service udev-trigger start
# rc-service udev-settle start
# rc-service udev-postmount start </nowiki>}}

If you want to use [https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ predictable network interface names], install eudev-netifnames. {{cmd|# apk add {{pkg|eudev-netifnames}}}}

== Remove ==

{{warning|Disabling eudev without setting up a different device manager may cause unexpected issues. If you install a different device manager with the setup script this step is not needed.}}

If you are not running in a chroot you need to stop the service first.{{cmd|<nowiki># rc-service udev stop
# rc-service udev-postmount stop</nowiki>}}

Then disable the services. {{cmd|<nowiki># rc-update delete udev sysinit
# rc-update delete udev-trigger sysinit
# rc-update delete udev-settle sysinit
# rc-update delete udev-postmount default</nowiki>}}

You might also want to uninstall the packages since they are not used anymore. {{cmd|# apk del {{pkg|eudev}} {{pkg|udev-init-scripts}}}}

== See also ==
* [[:Category:Device_Manager|Device Managers]]
* [https://wiki.gentoo.org/wiki/Eudev Gentoo wiki eudev]
* [https://wiki.archlinux.org/title/Udev Archwiki udev]
* [[Gamepad]]

[[Category:Device_Manager]]

Elogind

2024-05-23T12:22:34Z

Espindola: /* Hibernating */

[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}}
<nowiki>#</nowiki> rc-update add elogind
<nowiki>#</nowiki> rc-service elogind start}}
Polkit is used for authentication. Without it some things may not function. You need to install and configure [[D-Bus#Installation|D-Bus]] to use polkit.
{{Cmd|# apk add {{Pkg|polkit-elogind}}
<nowiki>#</nowiki> rc-update add polkit
<nowiki>#</nowiki> rc-service polkit start}}

Set up a [[PAM]] login.

== Hibernating ==

For {{Cmd|# loginctl hibernate}} to work, you must have a swap partition. Check {{Cmd|# lsblk}} for a partition with the mountpoint [SWAP].

<pre>
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 200M 0 part /boot
├─nvme0n1p2 259:2 0 100G 0 part /
├─nvme0n1p3 259:3 0 805G 0 part /home
└─nvme0n1p4 259:4 0 48.7G 0 part [SWAP]
</pre>

Remember also to add a kernel parameter to resume, ie in {{Path|/etc/default/grub}} :

{{Cat|/etc/default/grub|<nowiki>...
GRUB_CMDLINE_LINUX_DEFAULT="modules=sd-mod,usb-storage,ext4,nvme quiet rootfstype=ext4 resume=/dev/nvme0n1p4"
</nowiki>}}

Note the "resume=" flag with the same partition that was marked as [SWAP].

The resume process can be speed up reducing the size of the hibernation images. See the documentation for [https://docs.kernel.org/admin-guide/pm/sleep-states.html?highlight=image_size#basic-sysfs-interfaces-for-system-suspend-and-hibernation image_size] in the kernel docs for the details, but writing 0 to {{Path|/sys/power/image_size}} should make the images as small as possible.

== 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:

{{cat|/etc/elogind/logind.conf|...
[Login]
HandlePowerKey{{=}}suspend
...}}

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

== Doas ==

Doas is used to grant permissions for suspend-to-RAM and brightness control with brightnessctl:

apk add doas brightnessctl
# optionally, allow $USER root access with password
adduser $USER wheel

In <code>/etc/doas.conf</code>, set

permit :wheel
permit nopass $USER as root cmd /bin/loginctl
permit nopass $USER as root cmd /usr/bin/brightnessctl

After setting the above, suspend-to-RAM can be triggered by running

/bin/loginctl suspend

(use full path to executable) and brightness can be adjusted by running

/usr/bin/brightnessctl set 100

== See also ==
* [https://wiki.gentoo.org/wiki/Elogind elogind - Gentoo Wiki]
* [https://wiki.gentoo.org/wiki/Polkit polkit - Gentoo Wiki]
* [https://wiki.archlinux.org/title/Polkit polkit - ArchWiki]

[[Category:Desktop]]
[[Category:Seat_manager]]

Elogind

2024-05-23T12:21:24Z

Espindola: /* Hibernating */

[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}}
<nowiki>#</nowiki> rc-update add elogind
<nowiki>#</nowiki> rc-service elogind start}}
Polkit is used for authentication. Without it some things may not function. You need to install and configure [[D-Bus#Installation|D-Bus]] to use polkit.
{{Cmd|# apk add {{Pkg|polkit-elogind}}
<nowiki>#</nowiki> rc-update add polkit
<nowiki>#</nowiki> rc-service polkit start}}

Set up a [[PAM]] login.

== Hibernating ==

For {{Cmd|# loginctl hibernate}} to work, you must have a swap partition. Check {{Cmd|# lsblk}} for a partition with the mountpoint [SWAP].

<pre>
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 200M 0 part /boot
├─nvme0n1p2 259:2 0 100G 0 part /
├─nvme0n1p3 259:3 0 805G 0 part /home
└─nvme0n1p4 259:4 0 48.7G 0 part [SWAP]
</pre>

Remember also to add a kernel parameter to resume, ie in {{Path|/etc/default/grub}} :

{{Cat|/etc/default/grub|<nowiki>...
GRUB_CMDLINE_LINUX_DEFAULT="modules=sd-mod,usb-storage,ext4,nvme quiet rootfstype=ext4 resume=/dev/nvme0n1p4"
</nowiki>}}

Note the "resume=" flag with the same partition that was marked as [SWAP].

The resume process can be speed up reducing the size of the hibernation images. See the documentation for [https://docs.kernel.org/admin-guide/pm/sleep-states.html?highlight=image_size#basic-sysfs-interfaces-for-system-suspend-and-hibernation image_size] in the kernel docs for the details, but writing 0 to /sys/power/image_size should make the images as small as possible.

== 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:

{{cat|/etc/elogind/logind.conf|...
[Login]
HandlePowerKey{{=}}suspend
...}}

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

== Doas ==

Doas is used to grant permissions for suspend-to-RAM and brightness control with brightnessctl:

apk add doas brightnessctl
# optionally, allow $USER root access with password
adduser $USER wheel

In <code>/etc/doas.conf</code>, set

permit :wheel
permit nopass $USER as root cmd /bin/loginctl
permit nopass $USER as root cmd /usr/bin/brightnessctl

After setting the above, suspend-to-RAM can be triggered by running

/bin/loginctl suspend

(use full path to executable) and brightness can be adjusted by running

/usr/bin/brightnessctl set 100

== See also ==
* [https://wiki.gentoo.org/wiki/Elogind elogind - Gentoo Wiki]
* [https://wiki.gentoo.org/wiki/Polkit polkit - Gentoo Wiki]
* [https://wiki.archlinux.org/title/Polkit polkit - ArchWiki]

[[Category:Desktop]]
[[Category:Seat_manager]]

MDNS

2024-05-03T10:33:21Z

Espindola:

{{DISPLAYTITLE:mDNS}}
[https://en.wikipedia.org/wiki/Multicast_DNS Multicast DNS] is a protocol that is normally used for the discovery of printers. It is implemented by Avahi, but more setup is needed for the regular name resolution to see the results.

== Setup avahi ==

Install, enable and start avahi with:

{{cmd|doas apk add {{pkg|avahi}}
doas rc-update add avahi-daemon
doas rc-service avahi-daemon start}}

It should now be possible to browse results. To look for a printer, use:

{{cmd|doas apk add {{pkg|avahi-tools}}
avahi-browse --resolve --terminate _ipp._tcp}}

Make note of the hostname, as we will use it afterwards.

== Setup avahi2dns ==

Name resolution is implemented by musl, and it only supports DNS, so we have to map the avahi results to a regular DNS server. This is done by avahi2dns.

{{cmd|git clone https://github.com/LouisBrunner/avahi2dns
cd avahi2dns
go build
doas cp avahi2dns /usr/bin
doas cp openrc/avahi2dns /etc/init.d}}

since we will want a full DNS server running at port 53, we need to configure avahi2dns to use another port. Do that by creating {{path|/etc/conf.d/avahi2dns}} containing:

command_args="-p 5354"

Enable and start avahi2dns with

{{cmd|doas rc-update add avahi2dns
doas rc-service avahi2dns start}}

It should now be possible to use DNS to query the address of the printer.

{{cmd|drill -p 5354 @127.0.0.1 <printer_name>.local}}

Where printer_name is the hostname given by avahi-browse.

== Setup DNS resolver ==

We now need to setup a DNS resolver that will forward request of .local domain to avahi2dns and handle other requests normally. There is more than one way to do it, but we document an option that is probably most convenient for a laptop: using the DHCP provided server for the regular DNS requests. We will use unbound as the server and resolvconf to inform unbound about the DHCP results.

Install the programs:

{{cmd|doas apk add {{pkg|openresolv}} {{pkg|unbound}}}}

Create {{path|/etc/resolvconf.conf}}:

name_servers=127.0.0.1
unbound_conf=/etc/unbound-resolvconf.conf

This tells resolveconf to use a local nameserver and pass the DHCP provided DNS server to unbound

Create {{path|/etc/unbound/unbound.conf}}:

forward-zone:
name: "local"
forward-addr: 127.0.0.1@5354
include: "/etc/unbound-resolvconf.conf"
server:
do-not-query-localhost: no
domain-insecure: "local"

This reads the information provided by resolvconf, but forwards .local requests to avahi2dns. We also need to disable dnssec for .local and tell unbound that it is OK to query localhost.

Enable and start unbound

{{cmd|doas rc-update add unbound
doas rc-service unbound start}}

== Setup DHCP client ==

How send the DHCP provided DNS to resolvconf depends on the DHCP client being used.

=== udhcpc ===

This is the DHCP client in busybox, and will work for both wired and wireless interfaces.

Create {{path|/etc/udhcpc/udhcpc.conf}}:

RESOLV_CONF="/etc/udhcpc-resolv.conf"

Create {{path|/etc/udhcpc/post-bound/resolvconf}}:

#!/bin/sh
cat /etc/udhcpc-resolv.conf | resolvconf -a $interface

and make it executable

{{cmd|chmod 755 /etc/udhcpc/post-bound/resolvconf}}

An inconvenience of this setup is that udhcpc will not reconfigure the interface when connecting to other wifi networks. For that to happen one has to run

{{cmd|iwctl station wlan0 connect <network_name>
doas kill -USR2 $(cat /run/udhcpc.wlan0.pid)
doas kill -USR1 $(cat /run/udhcpc.wlan0.pid)}}

=== iwd ===

To avoid having to manually reconfigure the wifi interface, we can configure iwd to use DHCP internally and forward DNS server info to resolveconf. To do that create {{path|/etc/iwd/main.conf}}:

[General]
EnableNetworkConfiguration=True

[Network]
NameResolvingService=resolvconf

== Test the setup ==

You should now be able to query for both the printer address and regular addresses with

{{cmd|drill @127.0.0.1 <printer_name>.local
drill @127.0.0.1 alpinelinux.org}}

Your {{path|/etc/resolv.conf}} should also contain

nameserver 127.0.0.1

Printer discovery should now be working.

[[Category:Networking]]

MDNS

2024-05-03T10:22:56Z

Espindola:

{{DISPLAYTITLE:mDNS}}
[https://en.wikipedia.org/wiki/Multicast_DNS Multicast DNS] is a protocol that is normally used for the discovery of printers. It is implemented by Avahi, but more setup is needed for the regular name resolution to see the results.

== Setup avahi ==

Install, enable and start avahi with:

{{cmd|doas apk add {{pkg|avahi}}
doas rc-update add avahi-daemon
doas rc-service avahi-daemon start}}

It should now be possible to browse results. To look for a printer, use:

{{cmd|doas apk add {{pkg|avahi-tools}}
avahi-browse --resolve --terminate _ipp._tcp}}

Make note of the hostname, as we will use it afterwards.

== Setup avahi2dns ==

Name resolution is implemented by musl, and it only supports DNS, so we have to map the avahi results to a regular DNS server. This is done by avahi2dns.

{{cmd|git clone https://github.com/LouisBrunner/avahi2dns
cd avahi2dns
go build
doas cp avahi2dns /usr/bin
doas cp openrc/avahi2dns /etc/init.d}}

since we will want a full DNS server running at port 53, we need to configure avahi2dns to use another port. Do that by creating {{path|/etc/conf.d/avahi2dns}} containing:

command_args="-p 5354"

Enable and start avahi2dns with

{{cmd|doas rc-update add avahi2dns
doas rc-service avahi2dns start}}

It should now be possible to use DNS to query the address of the printer.

{{cmd|drill -p 5354 @127.0.0.1 <printer_name>.local}}

Where printer_name is the hostname given by avahi-browse.

== Setup DNS resolver ==

We now need to setup a DNS resolver that will forward request of .local domain to avahi2dns and handle other requests normally. There is more than one way to do it, but we document an option that is probably most convenient for a laptop: using the DHCP provided server for the regular DNS requests. We will use unbound as the server and resolvconf to inform unbound about the DHCP results.

Install the programs:

{{cmd|doas apk add {{pkg|openresolv}} {{pkg|unbound}}}}

Create {{path|/etc/resolvconf.conf}}:

name_servers=127.0.0.1
unbound_conf=/etc/unbound-resolvconf.conf

This tells resolveconf to use a local nameserver and pass the DHCP provided DNS server to unbound

Create {{path|/etc/unbound/unbound.conf}}:

forward-zone:
name: "local"
forward-addr: 127.0.0.1@5354
include: "/etc/unbound-resolvconf.conf"
server:
do-not-query-localhost: no
domain-insecure: "local"

This reads the information provided by resolvconf, but forwards .local requests to avahi2dns. We also need to disable dnssec for .local and tell unbound that it is OK to query localhost.

Enable and start unbound

{{cmd|doas rc-update add unbound
doas rc-service unbound start}}

== Setup DHCP client ==

How send the DHCP provided DNS to resolvconf depends on the DHCP client being used.

=== udhcpc ===

This is the DHCP client in busybox, and will work for both wired and wireless interfaces.

Create {{path|/etc/udhcpc/udhcpc.conf}}:

RESOLV_CONF="/etc/udhcpc-resolv.conf"

Create {{path|/etc/udhcpc/post-bound/resolvconf}}:

#!/bin/sh
cat /etc/udhcpc-resolv.conf | resolvconf -a $interface

An inconvenience of this setup is that udhcpc will not reconfigure the interface when connecting to other wifi networks. For that to happen one has to run

{{cmd|iwctl station wlan0 connect <network_name>
doas kill -USR2 $(cat /run/udhcpc.wlan0.pid)
doas kill -USR1 $(cat /run/udhcpc.wlan0.pid)}}

=== iwd ===

To avoid having to manually reconfigure the wifi interface, we can configure iwd to use DHCP internally and forward DNS server info to resolveconf. To do that create {{path|/etc/iwd/main.conf}}:

[General]
EnableNetworkConfiguration=True

[Network]
NameResolvingService=resolvconf

== Test the setup ==

You should now be able to query for both the printer address and regular addresses with

{{cmd|drill @127.0.0.1 <printer_name>.local
drill @127.0.0.1 alpinelinux.org}}

Your {{path|/etc/resolv.conf}} should also contain

nameserver 127.0.0.1

Printer discovery should now be working.

[[Category:Networking]]

MDNS

2023-12-26T17:36:16Z

Espindola:

[https://en.wikipedia.org/wiki/Multicast_DNS Multicast DNS] is a protocol that is normally used for the discovery of printers. It is implemented by Avahi, but more setup is needed for the regular name resolution to see the results.

== Setup avahi ==

Install, enable and start avahi with:

{{cmd|doas apk add {{pkg|avahi}}
doas rc-update add avahi-daemon
doas rc-service avahi-daemon start}}

It should now be possible to browse results. To look for a printer, use:

{{cmd|doas apk add {{pkg|avahi-tools}}
avahi-browse --resolve --terminate _ipp._tcp}}

Make note of the hostname, as we will use it afterwards.

== Setup avahi2dns ==

Name resolution is implemented by musl, and it only supports DNS, so we have to map the avahi results to a regular DNS server. This is done by avahi2dns.

{{cmd|git clone https://github.com/LouisBrunner/avahi2dns
cd avahi2dns
go build
doas cp avahi2dns /usr/bin
doas cp openrc/avahi2dns /etc/init.d}}

since we will want a full DNS server running at port 53, we need to configure avahi2dns to use another port. Do that by creating {{path|/etc/conf.d/avahi2dns}} containing:

command_args="-p 5354"

Enable and start avahi2dns with

{{cmd|doas rc-update add avahi-daemon
doas rc-service avahi-daemon start}}

It should now be possible to use DNS to query the address of the printer.

{{cmd|drill -p 5354 @127.0.0.1 <printer_name>.local}}

Where printer_name is the hostname given by avahi-browse.

== Setup DNS resolver ==

We now need to setup a DNS resolver that will forward request of .local domain to avahi2dns and handle other requests normally. There is more than one way to do it, but we document an option that is probably most convenient for a laptop: using the DHCP provided server for the regular DNS requests. We will use unbound as the server and resolvconf to inform unbound about the DHCP results.

Install the programs:

{{cmd|doas apk add {{pkg|openresolv}} {{pkg|unbound}}}}

Create {{path|/etc/resolvconf.conf}}:

name_servers=127.0.0.1
unbound_conf=/etc/unbound-resolvconf.conf

This tells resolveconf to use a local nameserver and pass the DHCP provided DNS server to unbound

Create {{path|/etc/unbound/unbound.conf}}:

forward-zone:
name: "local"
forward-addr: 127.0.0.1@5354
include: "/etc/unbound-resolvconf.conf"
server:
do-not-query-localhost: no
domain-insecure: "local"

This reads the information provided by resolvconf, but forwards .local requests to avahi2dns. We also need to disable dnssec for .local and tell unbound that it is OK to query localhost.

Enable and start unbound

{{cmd|doas rc-update add unbound
doas rc-service unbound start}}

== Setup DHCP client ==

How send the DHCP provided DNS to resolvconf depends on the DHCP client being used.

=== udhcpc ===

This is the DHCP client in busybox, and will work for both wired and wireless interfaces.

Create {{path|/etc/udhcpc/udhcpc.conf}}:

RESOLV_CONF="/etc/udhcpc-resolv.conf"

Create {{path|/etc/udhcpc/post-bound/resolvconf}}:

#!/bin/sh
cat /etc/udhcpc-resolv.conf | resolvconf -a $interface

An inconvenience of this setup is that udhcpc will not reconfigure the interface when connecting to other wifi networks. For that to happen one has to run

{{cmd|iwctl station wlan0 connect <network_name>
doas kill -USR2 $(cat /run/udhcpc.wlan0.pid)
doas kill -USR1 $(cat /run/udhcpc.wlan0.pid)}}

=== iwd ===

To avoid having to manually reconfigure the wifi interface, we can configure iwd to use DHCP internally and forward DNS server info to resolveconf. To do that create {{path|/etc/iwd/main.conf}}:

[General]
EnableNetworkConfiguration=True

[Network]
NameResolvingService=resolvconf

== Test the setup ==

You should now be able to query for both the printer address and regular addresses with

{{cmd|drill @127.0.0.1 <printer_name>.local
drill @127.0.0.1 alpinelinux.org}}

Your {{path|/etc/resolv.conf}} should also contain

nameserver 127.0.0.1

Printer discovery should now be working.

MDNS

2023-12-25T11:17:58Z

Espindola:

[https://en.wikipedia.org/wiki/Multicast_DNS Multicast DNS] is a protocol that is normally used for the discovery of printers. It is implemented by Avahi, but more setup is needed for the regular name resolution to see the results.

== Setup avahi ==

Install, enable and start avahi with:

{{cmd|doas apk add {{pkg|avahi}}
doas rc-update add avahi-daemon
doas rc-service avahi-daemon start}}

It should now be possible to browse results. To look for a printer, use:

{{cmd|doas apk add {{pkg|avahi-tools}}
avahi-browse --resolve --terminate _ipp._tcp}}

Make note of the hostname, as we will use it afterwards.

== Setup avahi2dns ==

Name resolution is implemented by musl, and it only supports DNS, so we have to map the avahi results to a regular DNS server. This is done by avahi2dns.

{{cmd|git clone https://github.com/LouisBrunner/avahi2dns
cd avahi2dns
go build
doas cp avahi2dns /usr/bin
doas cp openrc/avahi2dns /etc/init.d}}

since we will want a full DNS server running at port 53, we need to configure avahi2dns to use another port. Do that by creating {{path|/etc/conf.d/avahi2dns}} containing:

command_args="-p 5354"

Enable and start avahi2dns with

{{cmd|doas rc-update add avahi-daemon
doas rc-service avahi-daemon start}}

It should now be possible to use DNS to query the address of the printer.

{{cmd|drill -p 5354 @127.0.0.1 <printer_name>.local}}

Where printer_name is the hostname given by avahi-browse.

We now need to setup a DNS resolver that will forward request of .local domain to avahi2dns and handle other requests normally. There is more than one way to do it, but we document an option that is probably most convenient for a laptop: using the DHCP provided server for the regular DNS requests. We will use unbound as the server and resolvconf and iwd to inform unbound about the DHCP results.

Install the programs:

{{cmd|doas apk add {{pkg|openresolv}} {{pkg|unbound}} {{pkg|iwd}}}}

Create {{path|/etc/resolvconf.conf}}:

name_servers=127.0.0.1
unbound_conf=/etc/unbound-resolvconf.conf

This tells resolveconf to use a local nameserver and pass the DHCP provided DNS server to unbound

Create {{path|/etc/unbound/unbound.conf}}:

forward-zone:
name: "local"
forward-addr: 127.0.0.1@5354
include: "/etc/unbound-resolvconf.conf"
server:
do-not-query-localhost: no
domain-insecure: "local"

This reads the information provided by resolvconf, but forwards .local requests to avahi2dns. We also need to disable dnssec for .local and tell unbound that it is OK to query localhost.

And the last config charge is to have iwd forward DNS server info to resolveconf. To do that create {{path|/etc/iwd/main.conf}}:

[Network]
NameResolvingService=resolvconf

Enable and start unbound

{{cmd|doas rc-update add unbound
doas rc-service unbound start}}

Reconnect to your wifi. You should now be able to query for both the printer address and regular addresses with

{{cmd|drill @127.0.0.1 <printer_name>.local
drill @127.0.0.1 alpinelinux.org}}

Your {{path|/etc/resolv.conf}} should also contain

nameserver 127.0.0.1

Printer discovery should now be working.

MDNS

2023-12-17T20:31:50Z

Espindola: Created page with "[https://en.wikipedia.org/wiki/Multicast_DNS Multicast DNS] is a protocol that is normally used for the discovery of printers. It is implemented by Avahi, but more setup is needed for the regular name resolution to see the results. == Setup avahi == Install, enable and start avahi with: sudo apk add avahi sudo rc-update add avahi-daemon sudo rc-service avahi-daemon start It should now be possible to browse results. To look for a printer, use: sudo apk add avahi-..."

[https://en.wikipedia.org/wiki/Multicast_DNS Multicast DNS] is a protocol that is normally used for the discovery of printers. It is implemented by Avahi, but more setup is needed for the regular name resolution to see the results.

== Setup avahi ==

Install, enable and start avahi with:

sudo apk add avahi
sudo rc-update add avahi-daemon
sudo rc-service avahi-daemon start

It should now be possible to browse results. To look for a printer, use:

sudo apk add avahi-tools
avahi-browse --resolve --terminate _ipp._tcp

Make note of the hostname, as we will use it afterwards.

== Setup avahi2dns ==

Name resolution is implemented by musl, and it only supports dns, so we have to map the avahi results to a regular dns server. This is done by avahi2dns.

git clone https://github.com/LouisBrunner/avahi2dns
cd avahi2dns
go build
sudo cp avahi2dns /usr/bin
sudo cp openrc/avahi2dns /etc/init.d

since we will want a full dns server running at port 53, we need to configure avahi2dns to use another port. Do that by creating /etc/conf.d/avahi2dns containing

command_args="-p 5354"

Enable and start avahi2dns with

sudo rc-update add avahi-daemon
sudo rc-service avahi-daemon start

It should now be possible to use dns to query the address of the printer.

drill -p 5354 @127.0.0.1 <printer_name>.local

Where printer_name is the hostname given by avahi-browse.

We now need to setup a dns resolver that will forward request of .local domain to avahi2dns and handle other requests normally. There is more than one way to do it, but we document an option that is probably most convenient for a laptop: using the dhcp provided server for the regular dns requests. We will use unbound as the server and resolvconf and iwd to inform unbound about the dhcp results.

Install the programs:

apk add openresolv unbound iwd

Create /etc/resolvconf.conf:

name_servers=127.0.0.1
unbound_conf=/etc/unbound-resolvconf.conf

This tells resolveconf to use a local nameserver and pass the dhcp provided dns server to unbound

Create /etc/unbound/unbound.conf:

forward-zone:
name: "local"
forward-addr: 127.0.0.1@5354
include: "/etc/unbound-resolvconf.conf"
server:
do-not-query-localhost: no
domain-insecure: "local"

This reads the information provided by resolvconf, but forwards .local requests to avahi2dns. We also need to disable dnssec for .local and tell unbound that it is OK to query localhost.

And the last config charge is to have iwd forward dns server info to resolveconf. To do that create /etc/iwd/main.conf:

[Network]
NameResolvingService=resolvconf

Enable and start unbound

sudo rc-update add unbound
sudo rc-service unbound

Reconnect to your wifi. You should now be able to query for both the printer address and regular addresses with

drill @127.0.0.1 <printer_name>.local
drill @127.0.0.1 alpinelinux.org

Your /etc/resolv.conf should also contain

nameserver 127.0.0.1

So printer discovery should now be working.

Sway

2023-03-11T11:33:19Z

Espindola: Use the recommended way of starting wdg-desktop-portal-wlr.

[http://swaywm.org Sway] is a tiling [[Wayland]] compositor. It's a drop-in replacement for the i3 window manager.

== Installation ==

eudev:

<pre>
# apk add eudev
# setup-devd udev
</pre>

Graphics drivers:

* [[Intel Video]]
* [[Radeon Video]]
* [[Nvidia Video]]
Add user to the input and video groups:

<pre>
# adduser $USER input
# adduser $USER video
</pre>

Install some TTF fonts:

<pre>
# apk add ttf-dejavu
</pre>

seatd daemon:

<pre>
# apk add seatd
# rc-update add seatd
# rc-service seatd start
# adduser $USER seat
</pre>

Install sway:

<pre>
# apk add sway sway-doc
# apk add \ # Install optional dependencies:
xwayland \ # recommended for compatibility reasons
foot \ # default terminal emulator. Modify $term in config for a different one.
bemenu \ # wayland menu
swaylock swaylockd \ # lockscreen tool
swaybg \ # wallpaper daemon
swayidle # idle management (DPMS) daemon
</pre>

Configure [[Wayland#XDG_RUNTIME_DIR|XDG_RUNTIME_DIR]].

== Usage ==

For inter-program communication and functionality such as screensharing, install and enable dbus and PipeWire, see [[PipeWire]] and set <code>SWAYSOCK</code> environmental variable to the value exported by <code>sway</code>. In order to ensure that Pipewire and related services inherit the right environment variables, it is recommended to start these services via a process that is a direct descendant of sway itself.

Launch Sway with a D-Bus server available, use:

<pre>
dbus-run-session -- sway #prepend with exec in your login shell init script
</pre>

== Configuration ==

An example config is provided at <code>/etc/sway/config</code>. Copy it to <code>~/.config/sway/config</code> and read through it to learn the default keybindings.
Sway configuration is mostly backwards-compatible with that of [[I3wm|i3]] and if you are looking for a solution for a specific issue, you may also try checking if it hasn't been provided for i3WM.

For additional information, start at <code>man 5 sway</code> and read the [https://github.com/swaywm/sway/wiki upstream wiki].

=== Firefox screensharing ===

For some programs, additional configuration is needed to launch them natively under Wayland and to support special features such as screen sharing.

To launch Firefox natively under Wayland and to enable support for screensharing, you need:

* Install and configure [[PipeWire]]
* Install xdg-desktop-portal and xdg-desktop-portal-wlr package
* Install wofi for screen selection
* Launch pipewire on sway startup:
<pre>
exec /usr/libexec/pipewire-launcher
</pre>
* xdg-desktop-portal will start xdg-desktop-portal-wlr when needed, but needs a few environment variables. Add to the sway config:
<pre>
exec dbus-update-activation-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP=sway
</pre>
* Export the following variables:

<pre>
export MOZ_ENABLE_WAYLAND="1"
export XDG_CURRENT_DESKTOP=sway
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Flatpaks ===

Due to their sandboxing, flatpaks require the use of a portal frontend (xdg-desktop-portal) and backends (such as xdg-desktop-portal-wlr, xdg-desktop-gtk, xdg-desktop-portal-gnome) that implement the methods. When in doubt, install multiple backends. For more information on backends, see [https://github.com/flatpak/xdg-desktop-portal/#using-portals flatpak's page on the subject]. In addition to the steps under the "Firefox Screensharing" section, it may also be necessary to launch additional backends in your Sway config file. Otherwise, you may run into GDBus errors as your flatpak fails to interface with the portal. This can cause issues such as with opening your file directories from a flatpak application.

After installing different backends, you might need to add the relevant backends to your sway config file similarly to in the "Firefox Screensharing" section above. For example, an autostart section of your sway config file may include:
<pre>
exec /usr/libexec/xdg-desktop-portal-gtk
exec /usr/libexec/xdg-desktop-portal-wlr
exec /usr/libexec/xdg-desktop-portal-gnome
</pre>

This is only needed if they are not started automatically via other means.

=== Scaling for high resolution screens ===

Without further configuration, program interfaces might be too small to use on high resolution screens.

==== Via sway ====

Sway supports the per-display configuration of

* fractional (e.g., 1.5x), and
* integer scaling (e.g., 2x)

However, fractional scaling is discouraged due to both the performance impact and the blurry output it produces. In this case, where 1x scaling is too small and 2x scaling is too large, program-specific GTK/QT based scaling is recommended. See below.

To enable Sway scaling, the user can first preview different scaling factors with <code>wdisplays</code> package. Note the output name (eDP-1, LVDS-1) and try apply scaling factors such as 1 and 2. To make changes permanent, add

<pre>
output <name> scale <factor>
</pre>

to ~/.config/sway/config.

==== Via GTK/Qt ====

<pre>
# for GTK-based programs such as firefox and emacs:
export GDK_DPI_SCALE=2

# for QT-based programs
export QT_WAYLAND_FORCE_DPI="physical"
# or if still too small, use a custom DPI
export QT_WAYLAND_FORCE_DPI=192 # 2x scaling
export QT_QPA_PLATFORM="wayland-egl"
</pre>

=== Make clipboard content persistent ===
By default the clipboard content does not persist after terminating the program: you copy some text from Firefox and then exit Firefox, the copied text is also lost.

Install clipman from test repo and add the following to sway config:

<pre>
exec wl-paste --type text/plain --watch clipman store --histpath="~/.local/state/clipman-primary.json"
bindsym $mod+h exec clipman pick --tool wofi --histpath="~/.local/state/clipman-primary.json"
</pre>

=== Firefox picture-in-picture mode/floating windows ===
Add this to your sway config file (modify the numeric values to suit your needs and your display):
<pre>
for_window [app_id="firefox" title="^Picture-in-Picture$"] floating enable, move position 877 450, sticky enable, border none
</pre>

=== Screenshots ===
A simple tool that works well under Wayland is Grimshot. Example keybindings:
<pre>
bindsym Print exec grimshot copy area
bindsym Shift+Print exec grimshot copy screen
bindsym Control+Print exec grimshot save area ~/Pictures/$(date +%d-%m-%Y-%H-%M-%S).png
bindsym Control+Shift+Print exec grimshot save screen ~/Pictures/$(date +%d-%m-%Y-%H-%M-%S).png
</pre>

See [https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway the sway wiki's article] for a list of screenshot tools.

=== Start with NumLock enabled ===
Add this to your sway config file:
<code>input type:keyboard xkb_numlock enabled</code>

=== Change cursor theme and size ===
Add to your sway config:
<pre>
seat seat0 xcursor_theme my_cursor_theme my_cursor_size
</pre>
You can inspect their values with <code>echo $XCURSOR_SIZE</code> and <code>echo $XCURSOR_THEME</code>. If reloading your config does not result in change, try logging out and in.
{{Note|Wayland uses client-side cursors. It is possible that applications do not evaluate the values of <code>$XCURSOR_SIZE</code> and <code>$XCURSOR_THEME</code>.}}

=== Start as a service ===
Although this is not necessary, you may write an init script like the following:
<pre>
{{/etc/init.d/sway|
#!/sbin/openrc-run

description="Sway Compositor"

command="/usr/bin/sway"
command_args=""

pidfile="/run/sway.pid"

start_stop_daemon_args="--background --pidfile ${pidfile}"

depend() {
need localmount
after elogind
use seatd dbus
}
</pre>
Then as a root run <code>chmod +x /etc/init.d/seat</code> and <code>rc-update add sway default</code>. Make sure you have elogind installed or specify another service, like your display/login manager after which the sway service will run.

=== Custom keyboard layout ===

Since wayland does not support setxkbmap, you will also need to add similar content to your ''/usr/share/X11/xkb/rules/evdev.xml'', after <code></modelList></code> and after <code><layoutList></code>:
<pre>
<layout>
<configItem>
<name>[the name of your layout, same as the name of the file in /usr/share/X11/xkb/symbols]</name>
<shortDescription>[usually just two letters]</shortDescription>
<description>[description of your layout]</description>
<countryList>
<iso3166Id>US</iso3166Id>
<iso3166Id>NO</iso3166Id>
</countryList>
<languageList>
<iso639Id>eng</iso639Id>
</languageList>
</configItem>
</layout>

</pre>
Then, to enable for all keyboards, navigate to the input section of ''~/.config/sway/config'' and modify it to
<pre>
input * {
xkb_layout "my_layout"
}
</pre>
If you have enabled <code>xkb_numlock</code>, include this setting inside those braces as well.

== Troubleshooting ==

If you encounter any issues, try running <code>sway -Vc /etc/sway/config</code>. It will run sway with the default config file and set the output to be more verbose. It is generally a good idea to track your config files with git (when and if at all you use a remote repository for them, keep it private for security reasons).

=== Firefox (Flatpak) and/or GTK apps ===
==== Disappearing cursor ====
You may need to get an icon pack and possibly a theme from [https://www.pling.com/browse?cat=107&ord=latest Pling store] and set <code>GTK_THEME</code> environmental variable. Alternatively you can install a theme for all users (search [https://pkgs.alpinelinux.org/ Alpine Linux Packages] for ''*-icon-theme'') using <code>apk add</code>.

==== Missing file picker/cannot download ====

Go to ''about:config'' and set <code>widget.use-xdg-desktop-portal.file-picker</code> to 0.

=== Failing to start under certain graphics cards/multiple wlroots stacked windows spawning upon start ===
As of Dec 31 2022, [https://developer.nvidia.com/docs/drive/drive-os/latest/linux/sdk/common/topics/window_system_stub/Gnome-WaylandDesktopShellSupport136.html Nvidia still doesn't fully support Wayland]. Therefore, the possible solutions are as outlined in the link, or setting your WLR_BACKENDS environmental variables to <code>drm,libinput</code> or <code>x11</code> (add libinput here as well if you cannot use your mouse and keyboard after starting Sway). The latter also works for AMD/ATI cards ('''make sure to install libinput first''').

=== Sway socket not detected ===

See [[Sway#Installation|Installation]] for instructions on how to set this environmental variable. This issue may occur with terminal multiplexers, such as [[Tmux terminal multiplexer|tmux]]

=== Steam games launched via Proton crash before creating a window ===

Instead of just using the in-Steam menu to install and select a Proton version, try installing the flatpak community build for Proton onto your system. There are several versions, depending on your desired stability, and the experimental version available in Flathub is called "com.valvesoftware.Steam.CompatibilityTool.Proton-Exp". After you install your chosen version, go into Steam to specify compatibility tool for a game as usual. The installed community build will now be an option. Select that and try launching the game again.
[[Category:Desktop]]