From: karlheg@bittersweet.inetarena.com (Karl M. Hegbloom)
To: linux-kernel@vger.kernel.org
Subject: 2.4.0-test{8..11} CONFIG_NETLINK*=y => unresolved symbol errors in several modules
Date: 25 Nov 2000 00:22:15 -0800 [thread overview]
Message-ID: <8766lc1mx4.fsf@bittersweet.intra> (raw)
Sorry if this is already reported; I'm not subscribed since it's way
over my head still and there's too much else to do... so, please CC
me if you need more input.
I'm goofing around trying to get the right options set so I can run
`dhcpd' and `vtun'... I accidently turned on the "netlink" in
"networking options", and found that `depmod -a' mentions several
unresolved symbol errors. One module in particular is `ipchains.o'
that does this. Upon reboot and attempted `modprobe ipchains', I see
"netlink" mentioned, IIRC. There is conditionalization in the
"ipchains_core.c" on whether netlink is configured in, so I think
this is correct information.
Hope you can find it and fix it in only a few minutes. It will take
me another few years to do so, I believe.
-
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-25 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8766lc1mx4.fsf@bittersweet.intra \
--to=karlheg@bittersweet.inetarena.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