On Wednesday 06 June 2007, Kevin O'Gorman wrote:
> I had firestarter-1.0.3 emerged for quite some time. I hadn't really
> used it, but I'm a bit surprised now to find that it's interfering
> with normal emerges because it's got a big red "M" smacked on it.
>
> I suppose that means there's a problem with it, and it's explained in
> some forum or list that I don't normally get. But now I'd like a
> clue: what's the {prognosis, workaround, fix, alternative}. As I
> mentioned, I hadn't really started to use it, but I'd like to have a
> better firewall tool than building iptables scripts in vim.
I find it useful to read the new entries in
$PORTDIR/profile/package.mask after every sync to see what's recently
been nuked:
# Michael Sterrett <[EMAIL PROTECTED]> (30 May 2007)
# masked for removal on 20070629
# Upstream is dead and there are several open bugs:
# http://bugs.gentoo.org/show_bug.cgi?id=146620
# http://bugs.gentoo.org/show_bug.cgi?id=179792
# http://bugs.gentoo.org/show_bug.cgi?id=180104
# http://bugs.gentoo.org/show_bug.cgi?id=180105
# See
http://article.gmane.org/gmane.comp.security.firewalls.firestarter.user/1342
# for a thread on the mailing list regarding the state of things,
including
# mention of the problems with the newest netfilter code.
net-firewall/firestarter
alan
--
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?
Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
[EMAIL PROTECTED] mailing list
