public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Torrey Hoffman <thoffman@arnor.net>
To: Vincent Hanquez <tab@tuxfamily.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: (2.5.65) Unresolved symbols in modules?
Date: 17 Mar 2003 17:19:17 -0800	[thread overview]
Message-ID: <1047950384.12620.18.camel@rohan.arnor.net> (raw)
In-Reply-To: <20030318005612.GA1529@darwin.crans.org>

On Mon, 2003-03-17 at 16:56, Vincent Hanquez wrote:
> On Mon, Mar 17, 2003 at 04:46:57PM -0800, Torrey Hoffman wrote:
> > and then:
> > if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.5.65; fi
>                              ^^^^^^^^^^^^
> you seem to use old depmod (not /usr/local/sbin/depmod)

Ah, of course.  I followed the instructions that came with the
module-init-tools, and then just used "make modules_install".  
So much for following instructions.

I can only make the general observation that it would be helpful if:
- module-init-tools documentation pointed out this drawback of
installing to /usr/local/sbin
- module-init-tools documentation stated if it is or is not backward
compatible for the 2.4 kernels  (is it?)
- The kernel makefile used the module tools under /usr/local/sbin if
they exist.

(sigh)

Anyway, thanks again for the advice.

Torrey Hoffman
thoffman@arnor.net





  reply	other threads:[~2003-03-18  1:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18  0:46 (2.5.65) Unresolved symbols in modules? Torrey Hoffman
2003-03-18  0:56 ` Vincent Hanquez
2003-03-18  1:19   ` Torrey Hoffman [this message]
2003-03-18  1:27     ` Marijn Kruisselbrink
2003-03-19 21:29 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-03-18  1:11 Marijn Kruisselbrink
2003-03-18  3:18 ` Mike Galbraith
2003-03-18 11:13 Felipe Alfaro Solana

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=1047950384.12620.18.camel@rohan.arnor.net \
    --to=thoffman@arnor.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tab@tuxfamily.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