public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: georgek@netwrx1.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 Module compile error
Date: Sun, 07 Jan 2001 11:28:41 +1100	[thread overview]
Message-ID: <28137.978827321@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 06 Jan 2001 10:51:53 MDT." <f8je5tcv8fudipcjcfib41lacger7it6dv@4ax.com>

On Sat, 06 Jan 2001 10:51:53 -0600, 
George R. Kasica <georgek@netwrx1.com> wrote:
>Keith Owens wrote
>>You have a broken modules.conf that tells depmod to scan _all_ of
>>/lib/modules or you have an old version of modules or you have some
>>weird symlinks in /lib/modules.  It looks like you have some dangling
>>symlinks, although I cannot be certain about that.
>
>Here it is....what do I need to fix on it:
>>path[usb]=/lib/modules/`uname -r`/`uname -v`
>>path[usb]=/lib/modules/`uname -r`
>>path[usb]=/lib/modules/
>>path[usb]=/lib/modules/default

path[usb]=/lib/modules/ is the real killer, you scan all of
/lib/modules and pick up modules for every kernel.  Modutils 2.4 scans
all of /lib/modules/`uname -r` and its subdirectories by default.  You
do not need any path statements unless you have modules that are not
stored in the default path or its subdirectories.  IOW, remove all path
statements unless you are doing something really unusual.

-
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:[~2001-01-07  0:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 17:23 2.4.0 Module compile error George R. Kasica
2001-01-06  7:35 ` Keith Owens
2001-01-06 16:51   ` George R. Kasica
2001-01-07  0:28     ` Keith Owens [this message]
2001-01-06 16:54   ` George R. Kasica
2001-01-06 20:53     ` J . A . Magallon

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=28137.978827321@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=georgek@netwrx1.com \
    --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