3 ms·
Why not? Every executable is started with execve(2) syscall which takes an array of the environment variables that the kernel use to reset the process's environ
by Joker_vD 2y ago
Why not? Every executable is started with execve(2) syscall which takes an array of the environment variables that the kernel use to reset the process's environment variables it inherited from its parent, so obviously the kernel has full knowledge of the environment variables of all of the processes in the system.
Now, there is a reason why kernel actually does not have such knowledge, but it's not at all unreasonable to assume that the kernel has it.
- matheusmoreira 2y agoThe thing that really blows minds is the fact Linux does not do name resolution at all. Getting rid of glibc breaks a lot of stuff because everyone depends on glibc to do it. https://wiki.archlinux.org/title/Domain_name_resolution https://wiki.archlinux.org/title/Domain_name_resolution https://en.wikipedia.org/wiki/Name_Service_Switch https://en.wikipedia.org/wiki/Name_Service_Switch https://man.archlinux.org/man/getaddrinfo.3 https://man.archlinux.org/man/getaddrinfo.3