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.
Thread beginning with comment 497009
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: binary for windows....
by Alfman on Fri 11th Nov 2011 23:42 UTC in reply to "RE[2]: binary for windows.... "
Alfman
Member since:
2011-01-28

christian,

"All well and good until you find a critical bug in that DNS client library that every network capable program you have installed uses, and you now have to recompile (or relink at least) every single one of them."

Your point is well received.

However this person has a slightly different suggestion:

http://www.geek-central.gen.nz/peeves/shared_libs_harmful.html

He thinks applications shouldn't use shared libraries for anything which isn't part of the OS. This would largely mitigate DLL hell for unmanaged programs.

I realize this answer is gray and therefor unsatisfactory.


A better solution would be to have a standardized RPC mechanism to provide functionality for things like DNS. The glue code would be small, and could always be linked statically. This RPC would be kernel/user space agnostic, and could be repaired while remaining compatible. I think the shift from shared libraries to more explicit RPC interfaces would be beneficial, but it'd basically need a new OS designed to use it from the ground up - now that linux hosts tons of stable code, it's unlikely to happen.

Reply Parent Score: 2