linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Graegert" <graegerts@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: Autoloading modules after socket calls.
Date: Mon, 15 Jan 2007 16:43:07 +0100	[thread overview]
Message-ID: <6a00c8d50701150743h8587b98keb34f64c078c6cf1@mail.gmail.com> (raw)
In-Reply-To: <45AB9746.3040503@atl.lmco.com>

On 1/15/07, Jonathan Walsh <jwalsh@atl.lmco.com> wrote:
> I am not sure how used this list is, but it seemed like a good place to
> ask this sort of question.  I was wondering if there is a way to have
> the kernel autoload a module on a failed call to something that requires
> it.  For example if I have sctp compiled as a module, but not inserted,
> and I make a call to socket() requesting a IPPROTO_SCTP socket it will
> fail with EPROTONOSUPPORT.  Is there a way in some sort of kernel
> configuration of specifying that the sctp module should be swapped in at
> this point?  I could write code to pick up this error and insert the
> module myself, but I was hoping for a way for the kernel to
> automatically do it for me.

Jonathan,

maybe "kmod" is what you're looking for.  kmod performs background
monitoring and makes sure the required modules are loaded by modprobe
as soon as the respective functionality is needed in the kernel, but
it is not designed to unload modules automatically.

Simply activate the option 'Kernel module loader'  (CONFIG_KMOD) in
the kernel configuration.  It is available for both Kernel versions
2.4 and 2.6, respectively.

       \Steve

--

Steve Graegert <steve@graegert.com>
Jabber    xmpp://graegerts@jabber.org
Internet  http://eth0.graegert.com, http://blog.graegert.com

      reply	other threads:[~2007-01-15 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 15:01 Autoloading modules after socket calls Jonathan Walsh
2007-01-15 15:43 ` Steve Graegert [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a00c8d50701150743h8587b98keb34f64c078c6cf1@mail.gmail.com \
    --to=graegerts@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).