To: ELKS Mailinglist <linux-8086@vger.rutgers.edu>
Cc: "ELKS List" <linux-8086@vger.rutgers.edu>
From: Kevin Read <kread@weihenstephan.org>
Date: Sat, 12 Jul 1997 18:09:24 +0000 (GMT)
Newsgroups: linux.dev.8086
Hi ELKS people!
> About those dynamic libs, couldn't we put some sort of tag in the binary,
> placed by the compiler, telling the loader to load up to here, then, when
> some interrupt or whatever is issued, load to the next tag, using the
> same address space - voila, demand loading.
Actually the program needn't call an interrupt, just a kernel function or
syscall, telling the kernel (or sash?) loader part to load to the next tag.
Now these tags could be placed after initialization code or before extra,
seldom used parts of a program by the compiler, maybe user controlled.
Data would be kept across demand loading of course.
Hmm, what do you think? How does the loading stuff work with BigLinux? Do
they load the code in chunks of x pages or what do they do?
Or maybe we could put the loading information in the header, just saying
what blocks to load...
cu,
Obsidian aka Kevin Read
_
Creator of Worlds in VRML and RAYs \ / \
Dabbler in HTML / \ / \
Novice in C and Javascript / \ / \
User of Linux / / \ \ _ ?
Drinker of Cappuccino \ / / \ /|
Member of the Stigma group \ \ / / /
Laugher at Micro$cientology (TM) \ \ / / /
Member of the World Scout Movement / \/ \/
From Unofficial Linux-8086 Mailing List Archive (ULMLA)
Maintained by Robert
Robert's Mailing List Archive Page
Archive created with babymail