Timeline for Would an executable need an OS kernel to run?
Current License: CC BY-SA 4.0
34 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 24, 2018 at 19:26 | audit | First posts | |||
| Aug 25, 2018 at 5:07 | |||||
| Aug 21, 2018 at 23:21 | audit | First posts | |||
| Aug 21, 2018 at 23:21 | |||||
| Aug 18, 2018 at 10:51 | audit | First posts | |||
| Aug 18, 2018 at 10:51 | |||||
| Aug 17, 2018 at 22:15 | audit | First posts | |||
| Aug 17, 2018 at 22:17 | |||||
| S Aug 14, 2018 at 3:35 | history | suggested | Pang | CC BY-SA 4.0 |
Removed repeated "each". Improved punctuation marks.
|
| Aug 14, 2018 at 3:17 | review | Suggested edits | |||
| S Aug 14, 2018 at 3:35 | |||||
| Aug 7, 2018 at 16:09 | audit | First posts | |||
| Aug 7, 2018 at 16:10 | |||||
| Jul 31, 2018 at 16:07 | answer | added | cHao | timeline score: 1 | |
| Jul 31, 2018 at 6:47 | comment | added | Todd Wilcox | If you had asked this on the retro computing Stack, you would have gotten a lot of replies about how we used computers before hard drives were common. Many (most?) programs ran without an OS. You inserted the program disk, then turned on the computer, which booted right into the program itself. There was no exiting to an OS. When you were done, you turned off the computer. Or you could change disks and manually send the IPL (initial program load) interrupt, which on IBM PCs and compatible computers was done using CTRL-ALT-DEL. That would summarily restart the system and boot the new disk. | |
| Jul 30, 2018 at 8:56 | comment | added | millimoose | Or, of course, none of that needs to happen, because the C standard library implementation for an embedded device could include code that directly does the latter part, and the compiler for an embedded system will link everything statically so it is actually just a stream of instructions that directly execute on the CPU. But that's a special case for hardware that is usually run without an operating system, and you need a toolchain meant to do that. | |
| Jul 30, 2018 at 8:55 | comment | added | millimoose |
"with just a printf() function" - you're underestimating exactly how much complexity is hidden behind "call a function that does output". It's probably available through linking to a library - and a library ABI and linking is something the OS specifies and does when loading an executable - and to implement it an implementation of the C standard library might use syscalls that ask an OS kernel to write the data to devices.
|
|
| Jul 30, 2018 at 4:16 | comment | added | sawdust | @JörgWMittag -- If you're going to be pedantic, then why are you only scrutinizing just those terms and only this question? The truly salient term that needs defining is "operating system", which is questionably applied to MS-DOS (and similar single-task runtime environments). If there's a few (misinformed) people that think that the PC BIOS is an OS, then is everything up for grabs? I think not. The OP uses those words in a context that seems either reasonable (esp. if non-native English speaker) or non-technical. | |
| Jul 29, 2018 at 9:07 | comment | added | Jörg W Mittag | This really depends on your precise definition of the terms "executable", "kernel", "run", "need", "talk to", and "go through". Without a precise definition of those terms, the question is un-answerable. | |
| Jul 28, 2018 at 17:34 | vote | accept | GRANZER | ||
| Jul 28, 2018 at 15:28 | comment | added | Nonny Moose | This exists! (not affiliated, just thought it was cool) erikyyy.de/invaders | |
| Jul 28, 2018 at 14:37 | answer | added | Thorbjørn Ravn Andersen | timeline score: 2 | |
| Jul 28, 2018 at 12:03 | answer | added | Walter Mitty | timeline score: 2 | |
| Jul 28, 2018 at 9:49 | comment | added | abarnert |
printf is not a great example. It's explicitly defined by the C spec as a function that's only available in "hosted" implementations (meaning running on a kernel, as opposed to "freestanding", which may not require one). And on most platforms, printf is a just a function provided by your libc that does a bunch of stuff on your behalf (which eventually includes a syscall to print to stdout). It's really no different from calling libvlc_media_list_add_media or PyObject_GetAttr, except that some printf implementation is guaranteed linkable without adding extra non-standard -ls.
|
|
| Jul 28, 2018 at 8:26 | answer | added | Artelius | timeline score: 10 | |
| Jul 27, 2018 at 23:46 | answer | added | Gábor | timeline score: 3 | |
| S Jul 27, 2018 at 21:04 | history | suggested | Boann | CC BY-SA 4.0 |
grammar
|
| Jul 27, 2018 at 21:01 | history | tweeted | twitter.com/super_user/status/1022950086035292163 | ||
| Jul 27, 2018 at 20:32 | answer | added | sawdust | timeline score: 90 | |
| Jul 27, 2018 at 20:30 | answer | added | dgnuff | timeline score: 3 | |
| Jul 27, 2018 at 20:16 | comment | added | stib | If you're writing code for an Arduino you don't need an OS. | |
| Jul 27, 2018 at 20:05 | review | Suggested edits | |||
| S Jul 27, 2018 at 21:04 | |||||
| Jul 27, 2018 at 18:51 | answer | added | LawrenceC | timeline score: 4 | |
| Jul 27, 2018 at 18:37 | answer | added | Jamie Hanrahan | timeline score: 21 | |
| Jul 27, 2018 at 18:16 | answer | added | Alex | timeline score: 5 | |
| Jul 27, 2018 at 16:22 | answer | added | Mokubai♦ | timeline score: 40 | |
| Jul 27, 2018 at 15:50 | history | edited | gronostaj | CC BY-SA 4.0 |
Fix link
|
| Jul 27, 2018 at 15:48 | history | edited | GRANZER | CC BY-SA 4.0 |
added 1 character in body
|
| Jul 27, 2018 at 15:45 | review | First posts | |||
| Jul 27, 2018 at 16:11 | |||||
| Jul 27, 2018 at 15:41 | history | asked | GRANZER | CC BY-SA 4.0 |