It doesn’t work, but you led the path so I went env TERM=vt100 top but it also fails, with top: failed tty get … ^^
A normal terminal gets me a pts/0, but this kind gives me a ? (like all other processes btw).
I’m always up to understand/learn more, and why, but read below.
Ah good reminder, I already got the same warning about using xl console. Didn’t connect the dots !
Well, I ps aux --forest’ed this terminal and here is the result :
qrexec-fork-server (ppid 1)
\_ python3 qubes.StartApp qubes-run-terminal
\_ xterm
\_ bash
So the terminal is a bash shell running under xterm, is not a subprocess of X/Xorg, but isn’t it needing/using it nonethless ?
For example with ssh, there’s no xterm, only bash.
The context is that I’m trying to get the smallest system to run sys-net (and sys-fw afterwards).
I started using the official debian11-minimal, but Xorg is still there (the docs mention that so no surprise).
I could start from a debian netinst, but I’m not confortable enough with qubes tools to start this way ! And I still need remote control ^^