Timeline for Belated ascendancy of dynamic linkers
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 28, 2021 at 16:27 | history | suggested | Toby Speight | CC BY-SA 4.0 |
Spelling and grammar
|
| Mar 28, 2021 at 10:23 | review | Suggested edits | |||
| S Mar 28, 2021 at 16:27 | |||||
| Mar 27, 2021 at 21:43 | comment | added | dave | These days, some systems preload common shared libraries because (a) they assuredly will be needed, and (b) preloading at "preferred" address ranges reduces the need for per-process address fixups. | |
| Mar 27, 2021 at 18:50 | comment | added | Incnis Mrsi | @alephzero: a true library is (if necessary) loaded upon execution of a program. Things that are loaded beforehand are shared (although for IO.SYS and MSDOS.SYS the call mechanism technically differs), but are not libraries. BTW system calls are a thing distinct from simply library calls in modern OSes. | |
| Mar 27, 2021 at 17:48 | comment | added | alephzero | "MS-DOS wouldn't gain from shared libraries" - what exactly is the difference between "shared libraries" and IO.SYS and MSDOS.SYS - and any other TSRs ? | |
| Mar 27, 2021 at 17:12 | comment | added | Incnis Mrsi | The question is not about MS-DOS (which wouldn’t gain from shared libraries due to necessary complexity of memory management), but about such systems as Unix System V and early Linux (until libc3). | |
| Mar 27, 2021 at 16:41 | history | answered | Raffzahn | CC BY-SA 4.0 |