3 ms·
you can't move application launch logic to install time, it's inherently a launch time process - loading resources into memory, setting up runtime data structur
by dzdt 3y ago
you can't move application launch logic to install time, it's inherently a launch time process - loading resources into memory, setting up runtime data structures, etc
That is exactly what I want to do. Imagine your system had the full 64 bit address space populated with RAM. You launch every installed application simultaneously and let them run thru init to the point where they are ready for user interaction. Then suspend the whole system to disk. Thats what I want the "applications installed" state to look like.
In actual use you have limited RAM and launch applications one at a time. At launch time it is un-suspending the already initialized application. It has its own reserved virtual memory addresses so no need to reallocate new memory and no conflict with other running applications.
Emacs used to do something like this (maybe still does?) but in a very hacky way. I'd like it to be how the whole OS works.
- wbl 3y agoSmalltalk images are somewhat similar: the whole machine state is persisted.