C is just a thin wrapper around raw machine code, so naturally most of the details depend on the implementation. When a good C programmer wants to understand the stack, he leaps straight for the system documentation and source code for the target architecture. (A file named something like "crt0.s" or "fork.c" is a good place to learn how the stack works and where it comes from.) K&R is just background reading.