Timeline for Would an executable need an OS kernel to run?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2018 at 7:52 | audit | First posts | |||
| Aug 10, 2018 at 7:55 | |||||
| Aug 7, 2018 at 11:50 | audit | First posts | |||
| Aug 7, 2018 at 11:50 | |||||
| Aug 1, 2018 at 4:20 | comment | added | Stack Exchange Supports Israel | Since it may need to be explicitly stated in this question - do note that when we talk about programs "talking to" each other, it's metaphorical. | |
| Jul 28, 2018 at 5:26 | comment | added | jamesqf | Indeed, your terminal program doesn't even have to be running on the same machine as the program that's writing stuff to it. | |
| Jul 27, 2018 at 23:58 | comment | added | Chris Stratton | Not just hardware access, most communication between programs also goes through the kernel; that which doesn't typically at least involved the kernel is setting up a more direct channel. However, for purposes of the question, it is also possible and practiced in far simpler cases to condense all the code into a single program. | |
| Jul 27, 2018 at 16:22 | history | answered | Mokubai♦ | CC BY-SA 4.0 |