Shared runtime libraries - SV shared memory?

[n]

<munch>
	The way to do solve these problems are very much the same as VMS does it

	1.	Provide kernel support for mapping in the shared library (which 
		is after all just another sort of shared text, mapped at a
		different address, why not generalise this?) at exec time.

	2.	Make all the entry points into the library through a set of
		jump vectors (this way the entry point is always the same on
		many different versions of the library). This can be done by
		the same program that makes a stripped down library for linking.

	3.	Library data ... ugh ... the hard part, either rewrite the 
		routines so that they don't use it (the easy way out,
		unfortunatly there are many that already do this ... ie stdio)
		or provide a separate, copy-on-reference segment, also at a
		known address to store the data in.



			Paul Campbell		..!ucbvax!unisoft!paul