@blackhole, that kind of post do very little to narrowing the gap in "street cred" between yourself and @MiyoLinux.

I think you too should train your own (new) forum appearance towards Professional, Precise and Polite.

What is this about?

I'm not aware of any "cooldown time between searches" here?

To get an association table between PCI address and device node name, I think I might do:

ralph@stolpe:~$ realpath /sys/class/block/sd?/ 
/sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda
/sys/devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdb
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.1/2-1.1:1.0/host6/target6:0:0/6:0:0:0/block/sdc
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.4/2-1.4:1.0/host7/target7:0:0/7:0:0:0/block/sdd
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.2/2-1.2:1.0/host8/target8:0:0/8:0:0:0/block/sde

My example case shows 2 SATA disks and 3 USB disks. You may note that sdd and sde got enumerated in "wrong" order by the scsi module (relative to the USB host/port enumeration) for some reason. This appears to be consistent for that setup, but on occasion sdc and sdd are swapped, which is something I deal with by repeated monkey handson (= unplug+plugin) until order returns.

As @rolfie noted, the reason those "reorderings" happen is probably because the kernel+module code is multi-threaded with separate threads handling separate devices independently and these threads then compete and synchronize about "acquire the next device node name" on a first-come, first-served basis.

The answer to why it turns up as a new thing for you would probably be that the kernel+module code involved has been updated to include a more refined multi-threading in one way or another. Or, it might be hardware related that something has changed with some parts of the hardware due to aging, causing the startup timings to be slightly different now compared to how they have been previously. I think we can agree to that magic is not involved.

I guess it would be kernel related since it's the kernel modules that invent the names.

Or, does the naming coincide with PCI numbering?
Eg that the PCI address for /dev/sda is lesser than the PCI address for /dev/sdb ?

If the git directory on your system has pathname /home/user/mygitworkspace you would remove that git directory with the terminal command sequence:

$ cd /home/user
$ rm -rf mygitworkspace

Technically, "rm" is the program to run, "-rf" asks for the command variation to delete stuff recursively and force deletion to apply also for read-only files/directories, and "mygitworkspace" identifies the top-level pathname of files and directories to remove.

@steve_v, that kind of opinionated aggression is totally uncalled for. You may consider this a warning.

Again, the desktop iso is installer (not refracta) + a package pool, and the pool1 iso is only a package pool.

The desktop package pool contains some complete desktop package collections and then topped up with 2500 "most wanted" popcon packages, whereas the pool1 package pool merely is the 5000 most wanted packages.

In both cases the choice collection is filtered against currently available packages (at building time), expanded to include the first-options Depends and Recommends, and also including first-option choices for any so called "pure virtual" packages.

devuan_chimaera_4.0.0_i386_desktop.iso is an installer iso for an i386 architecture installation, plus a package pool that includes all packages including dependencies for a number of desktop installations.

devuan_chimaera_4.1_0_amd64_pool1.iso is a package pool only iso that doesn't contain the installer software. It contains the 5000 "most popular" packages for amd64 architecture installations according to popcon.debian.org at the date of the creation of the iso, plus their "depends" and "recommends".

@deepforest, why do you waste your time here?

By the looks of it, your devuan experience still leaves you so tremendously emotionally stressed that you end up with nonsense posts seemingly without purpose. Surely you have better things to do?

But maybe your purpose is really to ball-plank ideas on how to overcome whatever technical barrier you are currently at?

Indeed, there may well be people with knowledge and experience on that at this forum!

And to tap into that you simply just tune your manners more towards showing purpose and respect.

Currently I have duplicity at the top of my list of timeline backup methods as it's both fast and compact, and it's trivially easy to set up a cron job script that makes an incremental delta as often as I like.

I know of the front-end duply but only by name. (It's so rare that I need to peep into the backup)

Or you may need something like

        ip protocol icmp accept
        ip6 nexthdr ipv6-icmp accept
        ip protocol igmp accept

in the output filtering as well for ping responses.

Well I prefer the iptables rule syntax myself but if you prefer nftables then that's of course fine with me. Afaik, it's just a matter of syntax; either way it uses the kernel's network filtering rules, so I wouldn't be surprised if you can view the rules with iptables syntax or nftables syntax regardless of how you make the rules.

Whichever way, you need the input/output holes for 443 traffic similar to the current 80 or 22 traffic.