From: Adam Nielsen <a.nielsen@shikadi.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/2] New netfilter target to trigger LED devices
Date: Mon, 10 Nov 2008 21:55:57 +1000 [thread overview]
Message-ID: <4918214D.9070504@shikadi.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0811101156060.32764@fbirervta.pbzchgretzou.qr>
>> Does this mean I can remove those whole three lines? Or do I still need to
>> check the value of "invert" and complain if it's specified?
>
> You still need to check for it. If you grep for P_NO_INVERT in all .c
> files you will find the shortest possible line to do so.
Ah ok, that makes sense. On a related note, am I doing something wrong
here? Even when I'm not listing my target explicitly, I can get an odd
error:
$ iptables -A INPUT -j ACCEPT --test
iptables v1.4.2: Unknown arg `(null)'
> Even if the compiler could not, you could use sizeof("foo")-1 to get "3".
> That is a property of the C language.
Ha, been programming in it for years and never thought of doing that :-)
>> Maybe I should only allow alphanumerics and basic punctuation?
>
> I thought about that - but I have come to the conclusion that most
> character should be allowed so that people can use all the
> extended characters like CJK.
So if I switch to using double-quotes then, is there anything else I'll
need to escape? (such as '$')
>> That's fine, I've never used whatever that markup is before
>> (I don't even know what it's called...!)
>
> Read the PDF to the end and you will find out ;-)
Ah, I see now :-) That's a very useful and well written PDF too, btw.
Cheers,
Adam.
next prev parent reply other threads:[~2008-11-10 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 13:19 [PATCH 1/2] New netfilter target to trigger LED devices Adam Nielsen
2008-11-09 13:53 ` Jan Engelhardt
2008-11-10 10:34 ` Adam Nielsen
2008-11-10 11:10 ` Jan Engelhardt
2008-11-10 11:55 ` Adam Nielsen [this message]
2008-11-10 12:45 ` 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=4918214D.9070504@shikadi.net \
--to=a.nielsen@shikadi.net \
--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.