First try host deb.devuan.org which should give something like this:

deb.devuan.org is an alias for deb.rr.devuan.org.
deb.rr.devuan.org has address 160.16.137.156
deb.rr.devuan.org has address 5.9.122.185
deb.rr.devuan.org has address 185.178.192.43
deb.rr.devuan.org has address 198.58.118.8
deb.rr.devuan.org has address 114.34.81.84
deb.rr.devuan.org has address 94.16.114.15
deb.rr.devuan.org has address 185.236.240.103
deb.rr.devuan.org has address 5.161.180.234
deb.rr.devuan.org has address 67.219.104.166
deb.rr.devuan.org has address 23.169.200.138
deb.rr.devuan.org has address 147.229.176.19
deb.rr.devuan.org has address 152.53.121.155
deb.rr.devuan.org has address 131.188.12.211
deb.rr.devuan.org has address 147.78.194.22
deb.rr.devuan.org has address 195.85.215.180
deb.rr.devuan.org has address 103.146.168.12
deb.rr.devuan.org has address 95.216.15.86
deb.rr.devuan.org has address 200.236.31.1
deb.rr.devuan.org has address 46.4.50.2
deb.rr.devuan.org has address 130.225.254.116
deb.rr.devuan.org has address 141.84.43.19
deb.rr.devuan.org has address 190.64.49.124
deb.rr.devuan.org has IPv6 address 2001:e42:102:1704:160:16:137:156
deb.rr.devuan.org has IPv6 address 2a01:4f8:162:7293::14
deb.rr.devuan.org has IPv6 address 2a03:4000:28:24c::
deb.rr.devuan.org has IPv6 address 2a0d:eb00:8006::acab
deb.rr.devuan.org has IPv6 address 2a01:4ff:f0:dd3a::1
deb.rr.devuan.org has IPv6 address 2401:c080:2000:229e:4b70:fe82:36ed:f788
deb.rr.devuan.org has IPv6 address 2602:817:2000:401::138
deb.rr.devuan.org has IPv6 address 2001:67c:1220:8b0::93e5:b013
deb.rr.devuan.org has IPv6 address 2a0a:4cc0:c0:4676:4242:4242:4242:4242
deb.rr.devuan.org has IPv6 address 2001:638:a000:1021:21::1
deb.rr.devuan.org has IPv6 address 2a0a:e5c0:10:3::6eeb
deb.rr.devuan.org has IPv6 address 2a01:9e40::180
deb.rr.devuan.org has IPv6 address 2407:b6c0::12
deb.rr.devuan.org has IPv6 address 2a01:4f9:2a:fa9::2
deb.rr.devuan.org has IPv6 address 2801:82:80ff:8000::2
deb.rr.devuan.org has IPv6 address 2a01:4f8:140:1102:2b76:955d:b48f:bdf3
deb.rr.devuan.org has IPv6 address 2001:878:346::116
deb.rr.devuan.org has IPv6 address 2001:4ca0:4300::1:19
deb.rr.devuan.org has IPv6 address 2800:a8:c001::a

Then ping -c 1 each IP address to see which respond (you can probably ignore the IPv6 addresses). Or host 5.9.122.185 to find an addresses name.

Trying to connect to http://deb.devuan.org/merged in a browser is another useful check.

Once you find a working address put it into  /etc/apt/sources.list (keep notes though).

Edit: Crossposted with RedGreen925.

I should have said "But don't let non-root users write into the mountpoint."

By mountpoint I mean the directory in the root filesystem that the other filesystem is going to be mounted on. It does not need the same owner and permissions as the root of the filesystem that will be mounted on it.

Unless you get that clear in your head you will have big problems sorting out what is going on.

NB. It is possible to mount a filesystem on a directory in another mounted filesystem. But that's can cause problems if the intermediate filesystem isn't mounted when you want to mount the second filesystem aand is best avoided unless you have a good reason.

Swap placement will have no effect on performance on a SSD.

On spinning rust it will only have any effect if you are actually using swap space. Seeking from 1 cylinder to another takes longer if they are further apart, so having swap space near to the data files you are accessing at the same time will be slightly faster. But if you are using swap space that often your performance will feel very slow.

I learnt a lot about tuning disks and swap space when I was a MVS systems programmer (back then 64Mb was a big system). Nowadays I'd prefer to just buy more RAM (after checking for software with a memory leak).

Looking at your ping attempt I noticed:
You ping'ed dev.devuan.com which is wrong. As said above try deb.devuan.org (deb not dev and .org not .com).
DNS lookup for dev.devuan.com worked and got the same IP address as I did (199.59.243.227).
The ping didn't get a response for you, but I did when I tried it just now. But ping uses ICMP and devuan uses HTTP or HTTPS to get updates.

So try deb.devuan.org and post output if that fails. You might have ping blocked, you could check that by trying to get to http://deb.devuan.org in a broswer.

The first command the OP (really) should learn is man (short for manual) which tells you what a command does. info is similar but "enhanced" which makes it a bit harder to learn.

The first thing to do when someone/something recommends a command you don't know is to read the man page to see what it should do.

Start with:
man less (less is the pager man uses to display man pages).
man man
man apropos (this lets you search man pages for a given string).

As time passes you will build up a useful knowledge base of UNIX/Linux commands.

Reading another forum I found:

I've copied that rather than posting a link because you have to register to read that forum. And there's not much else there relevant to you. But I though that might help.

It's at https://www.mersenneforum.org/node/2301 … ost1061326 is you want to read it though.

Try df -k /var/run/ and ls -lid /var/run
On my system /var/run/ is a symlink to /run which is a tmpfs. So it's contents will be re-created at every reboot, which will make the -i flag vanish (tmpfs is a filesystem that only exists in ram).

That would explain why chattr -i didn't seem to work. Checking with lsattr might be interesting too.

I doubt wayland would do any better. It looks as if the game has a memory leak, which will probably still happen under wayland.

The only quick fix I can think of is to only run the game for a limited time, then quit it and restart wine before running it again. If it's the sort of game where you can do that.

Yes, I normally disable javascript, for safety. I've managed  to get it now.

Running sort <ps.out1 -g -k 8 | tail against each file in turn to find the programs with biggest RSS I spotted two large users:

R userus+  3114     1 99  80   0 2193540 2241107 -  08:48 ?        00:28:46 C:\Program Files (x86)\StarCraft II\Versions\Base92440\SC2_x64.exe
R userus+  2936  2935 62  80   0 2250356 901302 -   08:48 tty1     00:14:23 /usr/lib/xorg/Xorg -nolisten tcp :0 vt1 -keeptty -auth /tmp/serverauth.LPffKQyAqd

(those are in ps4)
/usr/lib/xorg/Xorg is probably innocent.
C:\Program Files (x86)\StarCraft II\Versions\Base92440\SC2_x64.exe is the most likely culprit.

HTH.

Check what happens if you put a program called poweroff in your path that does something else. Eg the following:

#!/bin/bash
echo In fake poweroff script
id

If that says it's running as root you have a security hole. A malicious person could add something like rm -rF / to it.

Try chattr -i on the file the symlink points to. That might work.

Or (as root):
ls -l /etc/resolv.conf
# Note where it points to (I'll use dest below).
rm /etc/resolv.conf
mv dest /etc/resolv.conf
That should turn /etc/resolv.conf back into a normal file.

The first step is to read the man (or info) pages for free and vmstat. They describe what the output fields mean.

Memory leaks can be a pain to track down. To find out which program is leaking memory you may need to:
ps -efly >ps.out1
Run suspect program (in your case the game under wine) for a while.
ps -efly >ps.out2
Run the program for a bit more.
ps -efly >ps.out3
...
When the system starts paging take a last snapshot:
ps -efly >ps.outn
Then stop the program and compare memory snapshots to see which program(s) RSS and SIZE fields were growing.

Then *all* you have to do is to find who supports the leaky program and persuade them to fix it.

Caveat. I've not had to do that myself, so I can't be sure it will work.