alt Hacker News... and the question was: "Why doesn't the kernel look at PATH"
It's not a "shell construct" either, the standard execvp libc function looks at PATH.
Replies
stabbles • today at 10:15 AM
Indeed, it's a libc construct.
... and the question was: "Why doesn't the kernel look at PATH"
It's not a "shell construct" either, the standard execvp libc function looks at PATH.
Indeed, it's a libc construct.
A surprising number of things in Linux are transparent to the kernel as they are implemented in user space. For instance, the Linux kernel doesn't support multithreading. It only supports processes sharing an address space. Which is what most people call threads - but in the kernel, they are just processes that happen to share an address space.