To do this, you will need a smart controller that switches which port it’s talking to.
Or you can stick a relatively cheap device on every mini and and connect it to the network.
Having a “controller” for every mini means you can swap single units in both hardware and software very easily. There’s a one-to-one relationship and you don’t have to deal with pairing.
Is video forwarding part of the product offering, or simply considered required for management functions?
Either way, I probably agree that a raspi per unit probably makes sense at a scale of a few dozen racks, but it would be interesting to do the math on when it would be price-efficient to have a 1:n management node scheme. I don't imagine there are many USB-C hubs that support being display sinks on the downstream ports (if that's even possible at all) but perhaps you could use an FPGA to synthesize a small ARM core with a bunch of native USB-C interfaces capable of doing it?
Simple... they're (likely) running something on the Raspberry Pi's that sets them up as USB gadgets, aka the Mac Mini "sees" a virtual keyboard and mouse. That's enough to manage remote provisioning.
To replicate that they'd need a KVM switch which doesn't have some weird edge case in how exactly it does USB-C switching, and it needs to be remotely controlled. A Pi is cheaper plus the failure modes of a Pi are more understood than the failure mode of some weird ass KVM switch someone cobbled together in China.
>/sys/power/s_stats is peripheral in terms of antico grego and a shallow-clientx .async language in thread_entry, arg