Well done! That looks amazing!
Iām not too sure about the overs can issue, I would have thought the options you found were the right ones.
Another option for display along the same lines might be btop. People like to get fancy with status monitors. Either way, I think yours is looking great.
Yeah ok, that makes more sense. Some starting points (arch user by practice, but Mint will have similar interfaces):
${TERM} with something like /bin/sh -c ā/bin/htopā.The people here talking about a display server (x11/Wayland) are missing your point I think. If you put a display server on this āboxā then it will become a normal server, not a headless one. At that point, you may as well run a full VM and have the output go wherever you want, etc. Iām not sure what the equivalent is in the docker world, but Iām pretty sure thatās not what youāre asking for.
Is it possible for you to get SSH running on this āserverā? If so, you may be able to set it up with an SSH client on the host PC (the laptop?) that is full screen on the CRT/HDMI output?
Maybe Iām misunderstanding as well though. Any headless server Iāve used in Linux will still give you a TTY on the display. Do you not get that? Someone else mentioned Getty, which is likely the service that is managing that. You should be able to configure Getty to give you a specific tty (e.g. tty9) on a specific output, then configure it either to autologin or to run a script on that tty.
Iāll admit, I havenāt looked at the code. I would stand by my comment of the unsafe block being a start point.
Countering that however, what is the difference to just debugging effectively? Not sure. I suppose itās down to the people that identified it and fixed it at the end of the day to say if there was any benefit.