<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 08.00.0681.000">
<TITLE>Semantics & mechanism of "preloaded" modules</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Hi there,</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">We</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> just came across a feature we didn</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">t find documented in</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">enough</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">detail</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">–</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"></FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">namely</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> the feature of preloading modules.</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"></FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">Could someone shed some light on the semantics and mechanism of preloaded modules?</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Background: we wanted to turn on</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">the</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">debug output in module prim_inet</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">only</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">to find</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> that</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> it wouldn</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">t report anything. We</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">eventually</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"></FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">stumbled over the fact that this module is p</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">reloaded and that it</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">s part of a sticky directory. We then</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">found the</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">–</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">nostick option to (re)load our version of the module prim_inet</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">, which got us the output we expected.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">We</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">d</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">love</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> to understand where the preloaded module beams are stored and how we could have our</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri"> version of the module preloaded!?</FONT></SPAN><SPAN LANG="en-us"> <FONT FACE="Calibri">My guess is that preloaded modules are included in the boot script and thus we</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">’</FONT></SPAN><SPAN LANG="en-us"><FONT FACE="Calibri">d simply have to regenerate the script?</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Calibri">Thanks & cheerio, Harry.</FONT></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"></SPAN></P>
</BODY>
</HTML>