*** This bug is a duplicate of bug 78017 ***
https://bugs.launchpad.net/bugs/78017
What my boss worked out was the following:
Grab the "bash" file from /bin on a Edgy (or dapper) box/install.
Rename this to bash31 and move to /bin on your Fiesty box.
Then change the first line of your fireh
How did you do that Johanathon, I cat get it to work, maybe I am missing
something, I have a GNU bash, version 3.1.17(1)-release on a dapper box,
so please tell me which files or dirs you moved, Thanks,
--
firehol does not work with bash 3.2 (which is default in feisty)
https://bugs.launchpad.net
We copied across the bash 3.1 binary from a Edgy box, changed the
scripts call to 3.1 and that's solved the issue, at least tempoarily. It
would be good if Bash could fix this, as it's their bug, not firehol.
Also, what is the status on this? Firehol is used on all of our
servers... It would be nic
Sadly, I don't think we will be seeing a fix for this anytime soon.
Firehol's project page has not been updated since Jan. 30, 2005 so I
don't think it's been currently maintained. Too bad since it was the
friendliest iptables front end that didn't limit you to a simple 2
interface setup.
I have
Showstopper for me too but seems nothing will be done with it :(
Sigh.
--
firehol does not work with bash 3.2 (which is default in feisty)
https://bugs.launchpad.net/bugs/90646
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
this bug is 17 days old and still has status unconfirmed and importance
undecided. For me, this absolutely is a showstopper.
What can we users do to speed up fixing this?
The upstream bugtracker mentioned by Tobias shows that this is not a bug
in firehol but in bash 3.2
For now I installed debia
