Re: glibc error reports go to the bit bucket in koji
How would mock go about capturing output sent directly to /dev/tty?
forkpty from <pty.h> is handy. In pythonland there is probably some other
simple canonical way to run a child in a pty.
Could we get away with hard/sym-linking it to /dev/stderr? Does this
have the potential to break other things?
Your kneecaps, fella, just try it.