> but for every envvar a program reads, something called setenv on it originally That's not true, that's just misunderstanding how it works. `execve()` takes a

> but for every envvar a program reads, something called setenv on it originally That's not true, that's just misunderstanding how it works. `execve()` takes an entirely new copy of environment variables to give to the child, that's the "real" way to do it.