[Firewall] Gawk... strictly required?

Philip A. Prindeville philipp_subx at redfish-solutions.com
Wed Mar 11 18:06:53 CET 2009

No, "cut" isn't adequate, we need awk. The wildcard_ifs() helper
function uses awk to drop the last character from the interface name
(the +).

It's just that a plain-vanilla V7 awk should be able to do the job.


Arno van Amersfoort wrote:
> You're right: we don't really need gawk. We could even only use cut as
> it can also do column selection etc. The only reason we need gawk is
> for fwfilter as it uses some gawk-specific stuff. I've removed the
> gawk dependency and changed it into just awk.
> a.
> Philip A. Prindeville wrote:
>> I just installed and ran 1.9.0c nightly build with Astlinux trunk (0.7
>> precursor), and it failed to start because gawk was missing.
>> I'm not sure that we're leveraging enough gawk-specific things to make
>> the firewall be that closely tied to gawk.
>> I remember trying to use ${foo:2:} to get substrings of $foo and was
>> told "that's too bash-specific", and changes have been made to have the
>> firewall run in a dash-only environment... so it seems like an odd
>> reversal of policy to be limited to gawk for no compelling reason.
>> Can we undo the dependency on gawk?
>> Thanks,
>> -Philip
>> _______________________________________________
>> Firewall mailing list
>> Firewall at rocky.eld.leidenuniv.nl
>> http://rocky.eld.leidenuniv.nl/mailman/listinfo/firewall
>> Arno's (Linux IPTABLES Firewall) Homepage:
>> http://rocky.eld.leidenuniv.nl

More information about the Firewall mailing list