From: gypsy <gypsy@iswest.com>
To: Jason Opperisano <Jopperisano@alphanumeric.com>,
netfilter <netfilter@lists.netfilter.org>
Subject: Re: Asking again: string match fails to find anything
Date: Wed, 21 Jul 2004 07:01:36 -0700 [thread overview]
Message-ID: <40FE7740.910371F4@iswest.com> (raw)
In-Reply-To: D5C9032B2B09C64EA2409D6214E91AC90511D3@asimail2.alphanumeric.com
Jason Opperisano wrote:
> Like I said--not an answer, but maybe someone else on the list can shed some light on your specific kernel/iptables/pom version and maybe a possible issue with string matching?
I'm pointing a finger at gcc 3.3.3 for lack of a better idea. It is one
of the commonalities on the 3 machines where I'm having problems.
1) Do you know what version of gcc compiled SuSE 9?
2) Did I miss something in POM? (Is there more than 1 version of string
match there?)
Thanks for your input!
Gypsy
next prev parent reply other threads:[~2004-07-21 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 7:30 Asking again: string match fails to find anything Jason Opperisano
2004-07-21 14:01 ` gypsy [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-20 18:37 Jason Opperisano
2004-07-21 6:07 ` gypsy
2004-07-20 13:56 gypsy
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=40FE7740.910371F4@iswest.com \
--to=gypsy@iswest.com \
--cc=Jopperisano@alphanumeric.com \
--cc=netfilter@lists.netfilter.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