The new version fixed kernel 2.6.20+ compatibility issues, fixed BASH 3.2 compatibility issues, and fixed various iptables compatibility issues along with other feature updates. See the official website for more details.
Attaching a patch: Also some notes: 1) In FILESDIR the init.d script is mislabeled. It is "firehol.initrd" but should be "firehol.init.d" 2) What is with the patching for new versions!? I removed that and used the stock tarball from upstream. 3) Had to change the ${S} because I didn't patch it.
Created attachment 120703 [details, diff] Diff for compatibility for new version
I have added the new version, please give it a try as soon as it is available on the mirrors. I did the following differently to what you had in the attachment: - I kept the patch for printf, not sure if this is fixed somehow differently in the upstream version and I was not able to verify, so I kept these changes for now - the name of firehol.initrd is just what is stored under "files", the "newinitd" in the ebuild names it correctly when installing into /etc/init.d/, or do I miss something here? - setting ${S} can go away completely - I use ${P} where possible again as we are using the latest version of firehol again
Yeah, I realized that I didn't really need ${S} anymore and was thinking about putting a patch up, but figured you smart devs would figure it out ;-) The reason I wanted to change the init.d script name is because it is deceiving in ${FILESDIR}. It makes it appear as though it is an initrd image(initial ramdisk) instead of a script. Just a matter of taste, I guess, but it might confuse a user.
