public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: initdata for modules?
Date: Mon, 27 Nov 2000 10:45:34 +1100	[thread overview]
Message-ID: <1887.975282334@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 26 Nov 2000 17:01:35 PDT." <20001126170135.A1787@vger.timpanogas.org>

On Sun, 26 Nov 2000 17:01:35 -0700, 
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org> wrote:
>insmod ppp_deflate (should trigger load of all these modules).  I 
>know it's works this way if there's a modules.dep file laying 
>around, but it would be nice for it to work this way without 
>needing the external text file.

There is a clean split between modprobe and insmod, modprobe is the
high level command that does all the fancy checking for inter module
dependencies, handling aliases and extracting options from
modules.conf.  insmod is the low level command that does exactly what
you tell it to do, no more, no less.  The only smarts that insmod has
is the ability to take a module name without '/' and find it using the
patchs in modules.conf.  That split between high and low level commands
is too useful to contaminate.

modules.conf already supports "above" and "below" commands for
non-standard dependencies.  The problem of not having a module.dep on
the first boot of a new kernel was addressed in kernel 2.4.0-test5 or
thereabouts, make modules_install runs depmod to build modules.dep
ready for the first boot.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-27  0:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 15:30 initdata for modules? Adam J. Richter
2000-11-26 22:54 ` Keith Owens
2000-11-27  0:01   ` Jeff V. Merkey
2000-11-26 23:45     ` Keith Owens [this message]
2000-11-27  2:45       ` Jeff V. Merkey
2000-11-27  7:35   ` Jakub Jelinek
  -- strict thread matches above, loose matches on Subject: below --
2000-11-26 23:47 Adam J. Richter
2000-11-27  2:49 ` Jeff V. Merkey
2000-11-27  2:06   ` Keith Owens
2000-11-27  3:27     ` Jeff V. Merkey

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=1887.975282334@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=adam@yggdrasil.com \
    --cc=jmerkey@vger.timpanogas.org \
    --cc=linux-kernel@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