Travis Bemann wrote:
> Should I try this with the newest CVS (and how do
> I get the right branch - I have no experience selecting CVS branches)?
Just pull the default, there is no experimental stuff going on anymore
AFAIK. The LENGTHY process (I added that warning as I had thought it had
a
Travis Bemann wrote:
> Should I try this with the newest CVS (and how do
> I get the right branch - I have no experience selecting CVS branches)?
Just pull the default, there is no experimental stuff going on anymore
AFAIK. The LENGTHY process (I added that warning as I had thought it had
al
On Mon, Sep 03, 2001 at 06:51:05PM +1200, David McNab wrote:
> Hi all,
>
> The first cut of fcpproxy (the stable fwproxy replacement) is now in cvs
> and ready for initial testing.
>
> As mentioned before, it's built on the robust JunkBusters proxy engine,
> and takes great liberties under GPL in
Hi all,
The first cut of fcpproxy (the stable fwproxy replacement) is now in cvs
and ready for initial testing.
As mentioned before, it's built on the robust JunkBusters proxy engine,
and takes great liberties under GPL in ransacking the JunkBusters code.
I didn't expect to have it done so soon.
On Mon, Sep 03, 2001 at 06:51:05PM +1200, David McNab wrote:
> The first cut of fcpproxy (the stable fwproxy replacement) is now in cvs
> and ready for initial testing.
Cool! Forgive me if any of these are already in there, but can I make
some feature suggestions?
1) Give good feedback to the us
