<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Kernel Modules in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-modules/m-p/2791955#M943413</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a set of kernel modules that are statically linked to the kernel. The kmsystem -q &lt;MODULE name=""&gt; displays the Loadable field of these modules as N.&lt;BR /&gt;Even the $LOADABLE value of these modules' system file in /stand/system.d/&lt;MODULE_NAME&gt; have the value N.&lt;BR /&gt;&lt;BR /&gt;However, when I use SAM to add these modules to the kernel, I get a new window asking me whether I would like to make these modules as loadable at boot time. This means that SAM would first link these modules statically to kernel by executing - 'kmsystem -l N module_name' and then adding these modules into /etc/loadmods. Next result is obvious - When the system comes after a reboot, it would start cribbing that I'm trying to add a module that's already there.&lt;BR /&gt;&lt;BR /&gt;Now the questions-&lt;BR /&gt;1. If a module's /stand/system.d/&lt;MODULE_NAME&gt; says $LOADABLE N, then does it mean it has to stay that way throughout, even when adding it to the kernel. Or in other words I cannot/shouldnot change the $LOADABLE flag to Y, either from the command line (with 'kmsystem -l Y') or from SAM?&lt;BR /&gt;2. Is there any other way to determine if a module is static apart from the kmsystem -q or the kmadmin commands?&lt;BR /&gt;3. Where can I find some documentation on the kernel modules? I've been through the kmadmin and kmsystem commands.&lt;BR /&gt;&lt;BR /&gt;I could sure use some help here.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sanjay&lt;/MODULE_NAME&gt;&lt;/MODULE_NAME&gt;&lt;/MODULE&gt;</description>
    <pubDate>Thu, 22 Aug 2002 15:19:58 GMT</pubDate>
    <dc:creator>Sanjay Yugal Kishore Ha</dc:creator>
    <dc:date>2002-08-22T15:19:58Z</dc:date>
    <item>
      <title>Kernel Modules</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-modules/m-p/2791955#M943413</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a set of kernel modules that are statically linked to the kernel. The kmsystem -q &lt;MODULE name=""&gt; displays the Loadable field of these modules as N.&lt;BR /&gt;Even the $LOADABLE value of these modules' system file in /stand/system.d/&lt;MODULE_NAME&gt; have the value N.&lt;BR /&gt;&lt;BR /&gt;However, when I use SAM to add these modules to the kernel, I get a new window asking me whether I would like to make these modules as loadable at boot time. This means that SAM would first link these modules statically to kernel by executing - 'kmsystem -l N module_name' and then adding these modules into /etc/loadmods. Next result is obvious - When the system comes after a reboot, it would start cribbing that I'm trying to add a module that's already there.&lt;BR /&gt;&lt;BR /&gt;Now the questions-&lt;BR /&gt;1. If a module's /stand/system.d/&lt;MODULE_NAME&gt; says $LOADABLE N, then does it mean it has to stay that way throughout, even when adding it to the kernel. Or in other words I cannot/shouldnot change the $LOADABLE flag to Y, either from the command line (with 'kmsystem -l Y') or from SAM?&lt;BR /&gt;2. Is there any other way to determine if a module is static apart from the kmsystem -q or the kmadmin commands?&lt;BR /&gt;3. Where can I find some documentation on the kernel modules? I've been through the kmadmin and kmsystem commands.&lt;BR /&gt;&lt;BR /&gt;I could sure use some help here.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sanjay&lt;/MODULE_NAME&gt;&lt;/MODULE_NAME&gt;&lt;/MODULE&gt;</description>
      <pubDate>Thu, 22 Aug 2002 15:19:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-modules/m-p/2791955#M943413</guid>
      <dc:creator>Sanjay Yugal Kishore Ha</dc:creator>
      <dc:date>2002-08-22T15:19:58Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel Modules</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/kernel-modules/m-p/2791956#M943414</link>
      <description>&lt;BR /&gt;Hi Sanjay,&lt;BR /&gt;&lt;BR /&gt;As no-one has answered...&lt;BR /&gt;&lt;BR /&gt;1) You can't actually change the loadable flag yourself. This field indicates "is this module loadable?". For instance, hpux 11i has some loadable drivers and tunables, for instance maxuprc. The /etc/loadmods file is for modules that you have loaded dynamically, but would like them to remain at that value/configuration after a reboot. In time, you will see more loadable modules. Using the command you specified would have no effect on non-loadable modules.&lt;BR /&gt;&lt;BR /&gt;2) Well, these are the tools specifically written for the new interface, so no, not by user-commands. Why would you want two ways to find out the same information? Also look at kmtune for the kernel tunables.&lt;BR /&gt;&lt;BR /&gt;3) Look in &lt;A href="http://www.docs.hp.com" target="_blank"&gt;www.docs.hp.com&lt;/A&gt; for more information. The links at the bottom of the index page, "all information for the .... release of hpux".&lt;BR /&gt;&lt;BR /&gt;If you are concerned about the way SAM displays this information, use the command line options. The SAM team work with a lot of different teams within HP so the interface may not be exactly as you expect. &lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;&lt;BR /&gt;James.</description>
      <pubDate>Thu, 22 Aug 2002 20:04:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/kernel-modules/m-p/2791956#M943414</guid>
      <dc:creator>James Murtagh</dc:creator>
      <dc:date>2002-08-22T20:04:56Z</dc:date>
    </item>
  </channel>
</rss>

