From: Eric Preston <eric@linuxmontreal.com>
To: David Ranch <dranch@juniper.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.20 - Possible module symbol bug
Date: Tue, 13 Nov 2001 16:17:34 -0500 [thread overview]
Message-ID: <20011113161734.A10370@firewall.imaginary.lan> (raw)
In-Reply-To: <3BEC4122.4C4DFB32@juniper.net>
In-Reply-To: <3BEC4122.4C4DFB32@juniper.net>; from dranch@juniper.net on Fri, Nov 09, 2001 at 12:48:34PM -0800
> #depmod -a
> /lib/modules/2.2.20/scsi/ide-scsi.o: unresolved symbol(s)
> /lib/modules/2.2.20/block/loop.o: unresolved symbol(s)
> /lib/modules/2.2.20/ipv4/ip_masq_vdolive.o: unresolved symbol(s)
> /lib/modules/2.2.20/ipv4/ip_masq_quake.o: unresolved symbol(s)
> /lib/modules/2.2.20/ipv4/ip_masq_raudio.o: unresolved symbol(s)
> /lib/modules/2.2.20/ipv4/ip_masq_irc.o: unresolved symbol(s)
> /lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol(s)
> /lib/modules/2.2.20/ipv4/ip_masq_user.o: unresolved symbol(s)
>
> #modprobe --debug ip_masq_ftp
> /lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_new
> /lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_put
> /lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_listen
> /lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_control_add
> /lib/modules/2.2.20/ipv4/ip_masq_ftp.o: unresolved symbol ip_masq_out_get
I noticed the same problem when recently building 2.2.20,
Enable "prompt for experimental code"
And choose the appropriate masq options that now appear,
and the masq stuff goes away. Something to do with CONFIG_MASQUERADE_MOD
not being set, was in a hurry so i didn't bother to look into it more,
regards,
Eric
prev parent reply other threads:[~2001-11-13 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 20:48 2.2.20 - Possible module symbol bug David Ranch
2001-11-10 6:28 ` Keith Owens
[not found] ` <Your message of "Fri, 09 Nov 2001 12:48:34 -0800." <3BEC4122.4C4DFB32@juniper.net>
2001-11-11 4:38 ` David Ranch
2001-11-11 6:03 ` Keith Owens
2001-11-13 21:17 ` Eric Preston [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=20011113161734.A10370@firewall.imaginary.lan \
--to=eric@linuxmontreal.com \
--cc=dranch@juniper.net \
--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