I used to make my own port for dwm, customised to my tastes. It's actually simpler than making De{bi,vu}an packages: https://www.openbsd.org/faq/ports/

The comp & xbase file sets are needed to make the port but they're part of the base system. There is a vanilla example available as well: https://github.com/openbsd/ports/tree/master/x11/dwm

EDIT: and suckless have already incorporated pledge(2) into the source code, which is nice.

https://git.suckless.org/dwm/file/dwm.c.html#l2146

https://unix.stackexchange.com/question … -same-uuid

@OP: search engines are quicker than forums

Is PA actually running?

pgrep -a pulse

No idea about Audacity though, I don't use that.

I don't think so.

From /usr/share/alsa/alsa.conf:

# pre-load the configuration files

@hooks [
   {
      func load
      files [
         "/var/lib/alsa/conf.d"
         "/usr/etc/alsa/conf.d"
         "/etc/alsa/conf.d"
         "/etc/asound.conf|||/usr/etc/asound.conf"
         "~/.asoundrc"
         {
            @func concat
            strings [
               {
                  @func getenv
                  vars [
                     XDG_CONFIG_HOME
                  ]
                  default "~/.config"
               }
               "/alsa/asoundrc"
            ]
         }
      ]
      errors false
   }
]

https://www.alsa-project.org/wiki/Asoundrc

And there's also https://wiki.archlinux.org/title/Advanc … chitecture & https://wiki.gentoo.org/wiki/ALSA

All I have ever needed to do is set the default card from HDMI to analogue to get both speaker output and microphone input working with firefox-esr in my Debian systems, as per the link kindly supplied by Camtaf.

What exactly do want ALSA to do? What sort of customisation is required?

Are you also using Xfce in Debian?

And is that the same kernel version as in your Debian system?

Do some benchmarks and find out for yourself. FWIW I use Arch with their linux-zen kernel, which has a similar patch set as the Liquorix kernels, but I can't notice any difference compared to the vanilla kernel version.

Did you check it was actually applied?

cat /proc/cmdline

You can also try acpi_backlight=video & acpi_backlight=native but they will only make a difference if you don't have an acpi_video0 directory in /sys/class/backlight/.

Do the xbacklight or brightnessctl packages work? You can bind keys to run those commands but if xev doesn't recognise the actual backlight keys then you'll have to use others.

For other backlight-related tips check the ArchWiki: https://wiki.archlinux.org/title/Backlight

I find GNOME to be the most effective in respect of backlight control with recalcitrant hardware so be sure to try https://wiki.archlinux.org/title/Backli … with_GNOME — the gdbus command is supplied by the libglib2.0-bin package.

Arch is a rolling release so the packages are always updated in synchrony. Testing/unstable are development branches so they just throw stuff at the wall and see what sticks.

The only problem with Arch (and by extension Artix) at the moment is their ancient glibc — it will go two versions behind when v2.35 is released tomorrow and they aren't applying patches. Gory details here. It's not a massive problem for me because I just use my laptop for recreational purposes but if you're using Artix for anything serious it might be best to look at Alpine instead (their musl libc is both up to date and inherently more secure than GNU's libc) because ceres/sid is also stuck on v2.33, albeit patched.

Back on topic with my Arch box:

It's almost exactly the same as last time but I've switched from xterm to foot. Caleb (one of the TUs) has very kindly adopted it and added it to [community], which is nice.

No, it didn't. Using just su leaves /sbin/ out of PATH and that's where shutdown is located. The *sigh* is because I've posted about this on these boards approximately 7,482 times and it is also featured in the release notes.

That command is supplied by the elogind package.

EDIT: https://wiki.debian.org/WhereIsIt

Try

loginctl poweroff

And also read my signature. *sighs*

What is the problem, exactly? Use <ctrl>+<alt>+F4 to see any error messages from the installer in full.

I will take a stab in the dark and guess that the system won't boot after installation?

If that is the case then use the "expert" installation and select "force extra installation to the EFI removable media path" in the GRUB options.

For an already installed system use rescue mode to obtain a shell in the installed system then run

dpkg-reconfigure grub-efi-amd64

^ That should also offer the option described above.

Alternatively copy /EFI/devuan/shimx64.efi on the EFI system partition to /EFI/Boot/bootx64.efi and also copy /EFI/devuan/grubx64.efi to /EFI/Boot/ (all locations given relative to the ESP, which should be mounted under /boot/efi/ in the installed system).

If you use the last method then be sure to update the debconf database after booting into the new system:

# debconf-set-selections <<!
grub-efi-amd64 grub2/force_efi_extra_removable select true
!

Why not upgrade to beowulf or chimaera then? They have v90.0.4430.212 currently and it will be kept relatively up to date.

I don't think people should trust your links. If you want to engender trust then perhaps use an independent build service such as https://build.opensuse.org/ instead — that shows the build process for each hosted package, unlike your random download links.

The OBS only has options for Debian but the packages should be binary-compatible with the appropriate Devuan release.

Note that ~/.profile won't be read for LightDM.

Reference and potential solution: https://bugs.debian.org/cgi-bin/bugrepo … bug=752129

Good piece from Ariadne about this:

https://ariadne.space/2022/01/27/cve-2021-4034/

^ Lol. Indeed

So how did you install ceres then?

And what do you mean by "I lose Trash on Thunar", exactly? What behaviour do you expect to see and in what way does the observed behaviour differ?

You can use this to check what has been installed from that Skype repository:

aptitude search '?narrow(?installed, ?origin(. stable))'

^ That should just show skypeforlinux. Hopefully. I would just use chromium for Skype, or even the flatpak, but you might be comfortable handing over the keys to your system to the repository maintainers.