All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [Fwd: Re: Shortcuts to counting rules?]
Date: Mon, 03 Nov 2008 10:02:39 -0800	[thread overview]
Message-ID: <490F3CBF.5090706@hp.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0811010209040.23833@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Friday 2008-10-31 19:54, Rick Jones wrote:
> 
>>>iptables-save | grep ^- | wc -l
>>
>>Here is where I cop to being a luddite who prefers straight C to calling
>>system() :)
> 
> 
> But there is no C library. And libiptc is so strongly internal that
> it does not fall under libraries-to-use.

I'm willing to code without a library, I just need to know how to parse 
the set of entries I suspect.

Someone in netfilter suggested the getsockopt() calls were part of the 
ABI, which implies what the getsockopt() calls return is reasonably 
"stable."  Is that actually the case, or can one not even ass-u-me the 
getsockopt() calls themselves are stable?

>>>And strace should not be taught that. We have seen at least one
>>>change of the interpretation of the binary stream.
>>
>>How about at least the option name(s) so it can present something other than
>>the 0x40/0x41 etc?
> 
> 
> I do not mind that. Turn to the strace maintainer about getting that
> implemented.

Will do.

rick jones

  reply	other threads:[~2008-11-03 18:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 17:57 [Fwd: Re: Shortcuts to counting rules?] Rick Jones
2008-10-31 18:07 ` Jan Engelhardt
2008-10-31 18:54   ` Rick Jones
2008-11-01  1:10     ` Jan Engelhardt
2008-11-03 18:02       ` Rick Jones [this message]
2008-11-05 18:25       ` Jesper Dangaard Brouer
2008-11-05 18:55         ` Rick Jones
2008-11-05 20:36         ` Jesper Dangaard Brouer
2008-11-05 21:02           ` Rick Jones
2008-11-07  3:06         ` Jan Engelhardt
2008-11-08 10:28           ` Jesper Dangaard Brouer
2008-11-04  0:41   ` Philip Craig
2008-11-04  1:22     ` Jan Engelhardt

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=490F3CBF.5090706@hp.com \
    --to=rick.jones2@hp.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.