I have no idea.
I don't use it;
I just use plain ifupdown configurations, plus wpagui on some hosts.
I think of that as easy and straight-forward.
In particular, it's well documented.

what is PFS now? Is language too hard to be written in full?

If you want to boot the ISO in a VM, then obviously it is the VMs (emulated) hardware that is interesting, and not at all the host hardware.

So what does the "failsafe" boot use that is different from other boot options?

In which world are those two logs "much the same"??? Maybe in a world where you ignore differences...

@Atalnte: you should have installed the package printer-driver-escpr and not confused yourself and your system with dowwnloaded drivers. You will still need to go through the printer setup after installing the package.

github = Microsoft. Stay away!

You may check devuan repositories using pkginfo.devuan.org
For example, type https://pkginfo.devuan.org/qps to your browser.

Then, typically, a version code without "devuan" in it indicates that the package is directly a Debian package, whereas a package with "devuan" in it is a Devuan package; i.e., forked typically from Debian packaging sources, modified and built in the Devuan build pipeline and published in the Devuan specific repository overlay.

Find some other place for chatting please.

Don't copy AI output to here, @igorzwx, or anyone.

It appears you are using a VPN or http proxy where that VPN or proxy service is unhapy with the number of requests (per second?).

If that is the case, then you may need to choose a different provider; (I suppose it's technically possible to set up outbound bandwidth limitation but that might require working package system to get set up)

Interesting. So your great idea is that someone else should go and actually do something because you think it appears to be an easy thing?

The expert installer needs to go through the "load components" dialogue with an OK, but with or without selecting any additional components. Doing so will still load the  "default components", which includes various partman packages for different filesystems. Otherwise those "default components" are not loaded.

It's a fairly odd UX design, but the udeb involved is included straight from debian installer and noone has felt the urge to fork it only to deal with that quirk; there is always the issue of maintaining forks.