I have a doubt about deactivating firewall using Porteus Settings Centre (PSC).

The PSC scripts seems to manage activation and deactivation by setting or unsetting execution permission to file /etc/rc4.d/S-firewall.sh which it creates if doesn't exits.

So when you select 'Activate firewall when Porteus starts' checkbox the PSC script run a 'chmod +x /etc/rc.d/rc4.d/S-firewall.sh' command and if not checked it runs the same chmod command but with -x argument.

anyway, why using two models (slackware bsd scripts and slackware sysV-like scripts) to manage firewall activation at boot? wouldn't it be better for PSC to simply toggle x bit of /erc/rc.d/rc.FireWall file rather than create a sysV script file and toggle that (/etc/rc.d/rc4.d/S-firewall.sh)? and if doing that way using file S-firewall.sh I think PSC script should handle both files (rc,FireWall and S-firewall.sh), shouldn't it?

you're welcome, I'm happy helping to test porteus and make it better, the more I look at porteus internals the more I appreciate your hard & pretty work.

brokenman, I suppose using rc.FireWall makes unuseful the file S-firewall.sh so you can avoid the code to create it when not found, is it right? this way you end with a better script not having raw code for a file inside