To be clear: when/if interesting discussions emerge I would be keen to assist with improved platform software.

I set up a package mirror recently, and after a month++ it's sailing with these metrics

As you say, it only holds Devuan packages and it redirect to deb.debian.org for all Debian packages (as per the standard mirroring instructions).

The mirror is a Single-CPU VPS (qemu) with 1G RAM allotment by a "Tier 3" company.

https://pkginfo.devuan.org/gksu

I use ifupdown on its own.

But, yes, connman apparently includes DNS caching with built-in assumption that the network world is unchanging. Not that I know much about it; for me it turned up as a debian hack when wicd was abandoned, but there may well be more history to it than that.

The easiest and best (I say) is to just use traditional network configuration with ifupdown together with wpa_supplicant and possibly its wpagui gui tool,

EDIT: start with man interfaces

how about using

sudo reboot ; exit

There is no magic involved.

Installers that are fully contained within their initrd will be fully loaded by ventoy from their ISO files, and "work" provided that they don't require access to their media.

Installers that require access to their media will not have that access, because the media is not available as partitions with ventoy.

If such an an installer is made to look for a ventoy partition, to mount that filesystem, to search for their ISO among the collection of ISO image files, then it may well also work.

Good. I suppose that error code "-19" means something particular but I don't really know how to find out what. You might want to drop in to the #devuan IRC channel on lilbera.chat where you're likely to find people that knows about graphics.

You'll need to install hostapd and read through its documentation.

@Altoid, did you try installing when adding/keeping a chimaera sources.list line (in addition to daedalus)? or does that raise conflict with the "59" package?

I hope all my posts look interesting

Please, if you are posting links, then post links. Otherwise it's just an illegible mess of characters.

The way to find out is to use strace, focussing on the open or openat system calls and reducing it to the files concerned. Something like

$ strace -f -s 200 $program | sed '/open/!d;s|[^"]*"||;s|".*||' | sort -u

where $program is that program that handles the mouse click... your file browser(?).

EDIT: However if the click handling program farms out the decision logic to some dbus activated something, it breaks the call chain and becomes slightly more complext to trace. You might then need to trace dbus to work out where the decision logic is sited, and then set up a way to strace that.