Jan Engelhardt wrote:
Unrelated to this patch, but maybe the target would also be
better named "NAT" instead of the much more generic term "mangle".
Why is it using lower case letters btw?
No idea who has done this,
Lowercasing targets was the original author's (Bart De Schuymer's)
deed ;-)
I have nothing against lowercase targets, in fact, many a user seems
to so not get case-sensitity right — “INPUT” vs. “input” (built-in
chain names), “MASQUERADE” vs. “masquerade” (targets), to name some —
that I would support lowercasing all targets...— if it were not for
the clash between MARK (target) and mark (match), for example.
Though, calling one of them “mark_m” or underscore-something to avoid
the clash however, is what I dislike in favor of uppercasing target
names.
Its actually just exposing an implementation detail of how match
and target modules are located on the filesystem. The meaning
(match or target) can be deduced from "-j" and "-m".
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
