From: Harald Welte <laforge@netfilter.org>
To: linux-kernel@vger.kernel.org
Cc: Mike Fedyk <mfedyk@matchmail.com>
Subject: Re: Does CONFIG_NET_FASTROUTE conflict with CONFIG_NETFILTER?
Date: Sun, 4 Jan 2004 21:32:55 +0100 [thread overview]
Message-ID: <20040104203255.GC830@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <20040104111154.GN1882@matchmail.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Sun, Jan 04, 2004 at 03:11:54AM -0800, Mike Fedyk wrote:
> If they do, then the config system should not allow you to enable both at
> the same time.
They don't conflict. It should compile quite fine, but you cannot use
both of them at the same time.
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-04 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 11:11 Mike Fedyk
2004-01-04 20:32 ` Harald Welte [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=20040104203255.GC830@obroa-skai.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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®