Looks like the OP's mirror should still work:

~$ nslookup br.deb.devuan.org
Server:         9.9.9.9
Address:        9.9.9.9#53

Non-authoritative answer:
br.deb.devuan.org       canonical name = pkgmaster.devuan.org.
Name:   pkgmaster.devuan.org
Address: 54.36.142.183
Name:   pkgmaster.devuan.org
Address: 2001:41d0:2:1f68::3624:8eb7

~$

I think it's using the DNS Round-Robin for deb.devuan.org but that's just an uneducated guess

Alpine apply a patch to eudev so that only root and members of the kvm group can edit the node: https://git.alpinelinux.org/aports/tree … ules.patch

You could create /etc/udev/rules.d/51-kvm.rules to do the same thing. But it would only work if the kvm group exists

The proposed-updates repository is for testing updates prior to point releases and so the packages may be buggy, the OP should therefore probably avoid them if they are using their system for anything critical. The backports repository has NotAutomatic: yes set in the InRelease file so no packages will be automatically updated from there unless the pinning is changed manually.

Better command:

grep kvm /etc/group

See also http://porkmail.org/era/unix/award.html#cat

Do you have QEMU installed? I think the qemu-kvm package creates that system group.

Does that use KVM for hardware virtualisation?

Complete fucking idiot. Or certified flight instructor, perhaps.

Anyway, an average user rating of 9/10 is pretty damn good and the sample size is big enough to make it fairly significant.

Devuan currently sits in 9th place overall: https://distrowatch.com/dwres.php?resou … average100

You removed the security repositories? Not sure that's wise... [/joke]

@OP: good choice.

Note that the nvidia-xconfig package is now obsolete because the X server in beowulf should automatically detect the proprietary driver. A configuration file should only be needed to specify particular options.

But I would never purchase hardware from those NVIDIA bastards so I'm not speaking from personal experience and anyway the proprietary drivers are not part of the official release so users are pretty much on their own.

I might be wrong but I think the network management program depends on the desktop. I know that GNOME uses NM and I think Plasma and Xfce do as well.

Anyway it's easy to change:

# apt install  wicd{,-{cli,curses,daemon,gtk}}- network-manager{,-gnome}

Not that I know of. See also http://forums.debian.net/viewtopic.php?f=10&t=125809

The startx command will launch a new graphical desktop on the same TTY from which the command is run so if you switch to TTY1 (with <ctrl>+<alt>+F1) then the desktop will be run from there. Note that you only need to use <alt>+F7 to get back to the original desktop if you're at a console (TTY) screen.

The display manager (the graphical login screen) will launch the graphical desktop on TTY7 by default (unless you're using GDM, which will launch it from TTY2 onwards).

No.

https://pkginfo.devuan.org/cgi-bin/d1pk … e=chimaera

Hmm, yes, sorry OP — you can't add your user to the sudo group if you can't use su

Rather than re-installing you can boot to a root shell by editing the bootloader: press either <tab> or <e> with the Devuan entry highlighted then replace ro with rw and add init=/bin/bash to the end of the line that starts with "linux"; use either <return> or <ctrl>+<x> to boot the modified entry.

I'm pretty sure your problem is due to the installer using a different keymap than your graphical desktop, this would cause you to enter the "wrong" password during installation.

Oh dear, I feel bad now — I actually know the original author of that guide from the BunsenLabs forums and their site is very good in general but that particular guide does have a few issues and it is somewhat outdated — my Debian packages are now linked directly from trizen's github page and so are considered "good enough" by the obmenu-generator creator.

You shouldn't blindly trust everything you read on the interweb