3 ms·
It discovers the location of `prompt-agent` from inside the Flatpak and executes it similarly to how it would execute a shell on your host. The socketpair() is
by audidude 3y ago
It discovers the location of `prompt-agent` from inside the Flatpak and executes it similarly to how it would execute a shell on your host. The socketpair() is passed in to do FD passing.
This of course only works because of careful selection of which GLibc API/ABI is allowed to be used. So far I've tested as far back as CentOS 7.
- jpeeler 3y agoI don't quite follow how the prompt-agent is assisting here. But more importantly, is said agent tied to prompt or could the "container detection extras" be usable with other Linux terminals?
- audidude 3y agoThe application runs inside of the Flatpak sandbox and therefore has a different mount namespace, PTY namespace, PID namespace, etc. That makes tracking foreground processes for simple things like "is the user running something when they close the tab other than the shell" extremely difficult. You'll just get 0 back a the PID from the TTY API. Additionally, being able to monitor container APIs in the long run will require more than file monitoring a podman json file in the user $HOME. It could connect to a socket for monitoring (like machinectl, etc). All these sort of things really benefit from running on the host rather than the UI sandbox. > is said agent tied to prompt or could the "container detection extras" be usable with other Linux terminals In that it's bundled with prompt, but it's just a D-Bus API albeit on a private socketpair(). The agent is not much code though to copy.