Linked by Thom Holwerda on Wed 9th Nov 2011 21:26 UTC, submitted by edwin
General Unix Way back in 2002, MIT decided it needed to start teaching a course in operating system engineering. As part of this course, students would write an exokernel on x86, using Sixth Edition Unix (V6) and John Lions' commentary as course material. This, however, posed problems.
Permalink for comment 497047
To read all comments associated with this story, please click here.
RE[7]: binary for windows....
by bogomipz on Sat 12th Nov 2011 16:35 UTC in reply to "RE[6]: binary for windows.... "
Member since:

Not really a kernel problem as the dynamic linker isn't really in the kernel.

Sorry, I should have said that the process of loading the binary is kept simple.

When something is statically linked, the library is dissolved, what is not used the dead stripper should remove.

Yes, this is why dynamic linking does not necessarily result in lower memory usage.

Your system is not like static linking. It's like baking dynamic linking.

This is where I do not know what you are talking about.

Creating a static library results in a library archive. When linking a program, the necessary parts are copied from the archive into the final binary. My idea was simple to postpone this last compilation step until install time, so that the version of the static library that the package manager has made available on the system is the one being used.

This way, the modularity advantage of dynamic linking could have been implemented without introducing the load time complexity we have today.

Reply Parent Score: 2