From: Harald Welte <laforge@gnumonks.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Barry K. Nathan" <barryn@pobox.com>,
Rusty Russell <rusty@linuxcare.com>, Marc Boucher <marc@mbsi.ca>,
James Morris <jmorris@intercode.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: test13pre2 - netfilter modiles compile failure
Date: Sat, 16 Dec 2000 11:57:05 +0100 [thread overview]
Message-ID: <20001216115705.A6797@coruscant.gnumonks.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10012160015521.11822-100000@penguin.transmeta.com> <Pine.LNX.4.10.10012160031450.11822-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10012160031450.11822-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Sat, Dec 16, 2000 at 12:42:53AM -0800
On Sat, Dec 16, 2000 at 12:42:53AM -0800, Linus Torvalds wrote:
>
> - the DRM "true library" solution, as shown by drivers/char/drm/Makefile.
>
> This is closest to what the code tried to do before, and might be the
> right solution for the "ip_nf_compat" module. However, it does result
> in the same code being duplicated in multiple modules. Not very nice.
mmh... but this is no real problem, because the ipchains and ipfwadm
backwards compat modules are mutually exclusive.
> - export more symbols (and mark the object files that export them as
> "export-objs"), so that they are visible across module boundaries.
> This is probably worth doing for at least the symbols
>
> register_firewall(), ip_fw_masq_timeouts() and
> unregister_firewall()
>
> so that "ipchains" and "ipfwadm" could just cleanly be separate modules
> on top of the "ip_fw_compat" module.
mmh.. but the ip_fw_compat layer without one of [ipchains, ipfwadm] doesn't
make sense at all. And ip_fw_compat is never going to be used more than once
because of the exclusiveness i've described above.
> Anyway, these kinds of things are really up to the netfilter people.
>
As no other netfilter core team member responded yet, I'm going to provide
a patch for the 'true library' solution.
> Linus
--
Live long and prosper
- Harald Welte / laforge@gnumonks.org http://www.gnumonks.org
============================================================================
GCS/E/IT d- s-: a-- C+++ UL++++$ P+++ L++++$ E--- W- N++ o? K- w--- O- M-
V-- PS+ PE-- Y+ PGP++ t++ 5-- !X !R tv-- b+++ DI? !D G+ e* h+ r% y+(*)
-
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/
next prev parent reply other threads:[~2000-12-16 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 4:56 Mohammad A. Haque
2000-12-16 5:52 ` Barry K. Nathan
2000-12-16 6:25 ` Linus Torvalds
2000-12-16 8:06 ` Barry K. Nathan
2000-12-16 8:23 ` Linus Torvalds
2000-12-16 8:42 ` Linus Torvalds
2000-12-16 10:57 ` Harald Welte [this message]
2000-12-16 13:09 ` Harald Welte
2000-12-16 17:51 ` Linus Torvalds
2000-12-17 2:43 ` test13pre2 - ieee1394 " Dax Kelson
2000-12-16 8:54 ` test13pre2 - netfilter modiles " Barry K. Nathan
2000-12-16 6:33 ` Andrew Morton
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=20001216115705.A6797@coruscant.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=barryn@pobox.com \
--cc=jmorris@intercode.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@mbsi.ca \
--cc=rusty@linuxcare.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®