I do not think an "auto-install" script is a good way forward here. Just provide a repository with instructions. The OBS even provides the instructions for you on their package download page. Creating an OBS repository doesn't need any scripting skills.

There is another way :-)

Open an account over at https://build.opensuse.org/ (it's free) then create a new subproject for Devuan with the dxvk package. Grab the original source tarball, the debian tarball and the .dsc file and add them to the dxvk subproject package page — that should be enough to build the package for Debian stable, and hence Devuan chimaera.

stevepusser has an excellent guide to the OBS over at forums.debian.net, you should search it out. The SUSE documentation is pretty good too, but very prolix.

Once the repository is working you can share a link here so everybody can use it.

Post back if you can't figure it out and I'll see if I can manage it. I'm trying to slim down on my OBS repositories because they recently complained I was using too much of their servers.

I think elogind is better than running X under root.

Doesn't seatd work in chimeara? I can get a Wayland session under Alpine with just that running. EDIT: with sway anyway.

Wouldn't running NM & ifupdown on the same interface cause potential conflicts? Why would you want both running?

Here's the follow up post about the purpose of RotaJakiro:

https://blog.netlab.360.com/rotajakiro_ … ceanlotus/

tl;dr: Linux copy of Mac's OceanLotus malware, probably funded by the Vietnamese government.

One liner to check infection:

# find / \( -name "gvfsd-helper" -o -name "systemd-daemon" \) -exec md5sum {} \;

The MD5 sums are available in the OP links.

Note that <alt>+F{whatever} only works from a console screen; <ctrl> is needed as well if used from a graphical desktop.

VT switching in Devuan has always worked as expected for me.

Using the raw file is fine but it will need to be kept updated.

Ceres now has the firmware from 2022-10-18 so you can use that.

Add this to /etc/apt/sources.list.d/ceres:

deb http://deb.devuan.org/merged ceres non-free

And add this to /etc/apt/preferences.d/ceres:

Package: *
Pin: release a=unstable, n=ceres
Pin-Priority: -1

Package: firmware-realtek
Pin: release a=unstable, n=ceres
Pin-Priority: 500

Then

# apt update
# apt upgrade

Keep checking chimaera-backports though because that package will probably make it through in a few weeks. When it does remove the added files and reinstall the package from backports instead.

That's just for the initramfs. Setting MODULES=dep wouldn't cause any firmware packages to be installed or removed.

# apt install isenkram
# isenkram-autoinstall-firmware

EDIT: or perhaps

# isenkram-pkginstall

I've never actually used it though.

If you had bothered to read my link then you would know that there is a difference:

systemctl mask apparmor.service

^ That disables the service and prevents it from ever being started again, even if another service calls it and even if dpkg tries to enable it (as it will do after apparmor is upgraded).

Please tell me how to make sysvinit do that. I am very curious.

Follow the advice given in my wiki link, here it is again:

# mkdir -p /etc/default/grub.d
# tee /etc/default/grub.d/apparmor.cfg >/dev/null <<<'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' 
# update-grub
# reboot

To re-enable AppArmor delete /etc/default/grub.d/apparmor.cfg and run the last two commands again.

I love a challenge but that's a step too far, even for me. Can we at least see the full error message? Or would that be considered cheating?