2. Then, it sets up the stack (for local variables, function params, etc) and the heap (for dynamic stuff you allocate with malloc()).
3. It configures default I/O, like stdin, stdout, and stderr.
4. Finally, it jumps to the entry point of code and hands over control to the program

Ever think about how your OS runs code?
1. The OS loads the program’s code and data from the disk into memory. It can do this eagerly (all at once) or lazily (only as needed).