
Contributed by Andreas Phlsson <andreas.pahlsson@tjohoo.se>


Some one _had_ to do this. (Why am I the one?) I wrote a initscript 
for fwbuilder scripts it works on my RedHat 7.1 system and it should 
be no problems with other init.d based systems.

Brief install documentation:
Become root (or use sudo...)
The <hostname>.fw file for the system goes in:
/etc/firewall/
The firewall file goes in:
/etc/init.d/
Add the service:
chkconfig --add firewall
Start the service:
/etc/init.d/firewall start
Done.

Known bugs/problems/features:
Script uses the hostname to choose .fw-file in /etc/firewall. If you use the correct hostname in fwbuilder you can just copy the result of the compilation to /etc/firewall. If you don't know your hostname (which you _should_ do) use just type 'hostname -s' in any available shell.
The start, stop, restart and status commands work.
The stop command makes the firewall drop ALL packets. If you not on 
console you will be cut off.


Changelog
010603
Fixed the initscript for firewall to use /etc/firewall/<hostname -s>.fw instead of /etc/firewall/*.fw.
Status is now working as expected.
