Enable the networking service to run the ifupdown scripts automatically at boot.

https://wiki.debian.org/WiFi/HowToUse#W … d_WPA2-PSK

Define "right". I much prefer /etc/network/interfaces over wicd or ceni, but then I prefer systemd-networkd over ifupdown so...

Please describe how you are attempting to make it work and what exactly happens when it doesn't work. Check the logs for errors and post them here if you can't figure out what they mean.

Ha! found it: http://forums.debian.net/viewtopic.php? … 09&start=0

Bug report: https://bugs.debian.org/cgi-bin/bugrepo … bug=925309

So try copying /boot/efi/EFI/devuan to /boot/efi/EFI/debian

EDIT: or perhaps use

# grub-install --target=x86_64-efi --bootloader-id=debian

www/firefox-esr in OpenBSD 6.6 has network.trr.mode set to "0" (zero), just like Devuan.

EDIT: upgraded to -current and the setting is the same.

How very strange

Is the EFI system partition definitely mounted under /boot/efi?

lsblk -f

Try changing /boot/efi/EFI/devuan/grub.cfg to this:

search.fs_uuid 9685be15-8423-402b-b734-f92844748a90 root hd0,gpt6
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

I'm booting via $ESP/EFI/BOOT/bootx64.efi using GRUB but there is no grub.cfg in $ESP/EFI/BOOT/ so I'm not sure if that's actually needed.

Can we see the content of that file please.

How did you do that, exactly?

And can we please see the output of

# parted --list
efibootmgr -v
/sbin/blkid

The boot-info-script package (/usr/sbin/bootinfoscript) will show exactly what's going on but I can't be bothered trawling through the wall-of-output so give me a few posts to work it out for myself first. Thanks.

^ Well that is interesting, I though I had misunderstood the network.trr.mode options but it seems otto@ has set it to "3" in OpenBSD, which would still use CloudFlare for portal detection and telemetry.

DoT ftw!

Read the documentation: https://www.gnu.org/software/shepherd/m … l#Services

Probably a lost cause though because it seems to be tightly integrated with herd.

EDIT: removed wind-up, it's not worth it.

The drivers for your wireless card are probably already included in the kernel but you might not have the (non-free) firmware that is required by your card.

What is your wireless hardware?

Well that is baffling

Have you tried something other than ping, for example:

sudo apt update

Perhaps your ISP is funny about ICMP requests. [/desperation]

I've never owned a printer but you can use this command to list enabled services and toggle their state:

# sysv-rc-conf

Disable the "cups" service with:

# sysv-rc-conf cups off

EDIT: typo.

What are you trying to pull? Is that pure malware or are you just advertising for your shitty company?

@all: *do not* follow the installation instructions, the .deb packages contain opaque binaries that do god-only-knows-what and the "configuration files" are complete nonsense.

Tethering does not require drivers.

I think fsmithred is referring to this package rather than your linked script.