Hi Paul,
There is no reason for it, that's why it's just available ;-)
http://leaf.sourceforge.net/bering-uclibc/index.php?module=pagemasterPAGE_user_op=view_pagePAGE_id=12MMN_position=32:32
ezipupd.lrp
Eric
Is there a reason the ez-ipupdate package for 3.x isn't in the packages
3.x list?
Eric Spakman wrote:
Hi Paul,
What troubles me more is that Tom updates the documentation on his site
to represent the state of the art in shorewall v5, and the currently
shipping versions of LEAF or BU are using shorewall v3, our
documentation will not match the code we're shipping.
snip
Doh, I'm an ass. I found it just after I sent the note out... I was
thinking, I know it was in 2.x...
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
Hi Paul,
What troubles me more is that Tom updates the documentation on his
site to represent the state of the art in shorewall v5, and the
currently shipping versions of LEAF or BU are using shorewall v3,
our documentation will not match the code we're shipping.
snip
There is no
On Thu, 2006-11-23 at 01:38, Eric Spakman wrote:
Ok, but back to the documentation issue. BU will always use the latest
stable shorewall version and even with an older version of BU it shouldn't
be a big problem to update to the latest shorewall (especially 3.0
onwards). Why duplicate the
Hello Mike,
Ok, but back to the documentation issue. BU will always use the latest
stable shorewall version and even with an older version of BU it
shouldn't be a big problem to update to the latest shorewall (especially
3.0
onwards). Why duplicate the shorewall documentation on the LEAF
On Thu, 2006-11-23 at 06:50, Eric Spakman wrote:
Hello Mike,
Ok, but back to the documentation issue. BU will always use the latest
stable shorewall version and even with an older version of BU it
shouldn't be a big problem to update to the latest shorewall (especially
3.0
onwards).
Hi Folks
let me please chime in
Mike Noyes wrote:
On Thu, 2006-11-23 at 01:38, Eric Spakman wrote:
Ok, but back to the documentation issue. BU will always use the latest
stable shorewall version and even with an older version of BU it shouldn't
be a big problem to update to the latest
On Thu, 2006-11-23 at 07:26, Eric Spakman wrote:
Hi Mike,
Eric,
Ah. We are in agreement then, or I think so. Do you still plan on a
shordoc package?
I don't know, a router/firewall is not really a good platform to read
documentation... Maybe Erich's suggestion will work, creating
On Thu, 2006-11-23 at 08:48, Mike Noyes wrote:
On Thu, 2006-11-23 at 07:26, Eric Spakman wrote:
I don't know, a router/firewall is not really a good platform to read
documentation... Maybe Erich's suggestion will work, creating some sort of
webconf plugin package (lwp) so the docs can be
Am Donnerstag, 23. November 2006 04:53 schrieb Greg Morgan:
Mike Noyes wrote:
snip
I found one (new?) problem:
And yet another problem. I was looking for your excellent introduction
to cvs as a developer the other day. Perhaps the SF interface changes
have broken all the doc manager
On Thu, 2006-11-23 at 12:21, KP Kirchdoerfer wrote:
Am Donnerstag, 23. November 2006 04:53 schrieb Greg Morgan:
Mike Noyes wrote:
snip
I found one (new?) problem:
And yet another problem. I was looking for your excellent introduction
to cvs as a developer the other day. Perhaps
Hi KP
KP Kirchdoerfer wrote:
Am Donnerstag, 23. November 2006 16:16 schrieb Erich Titl:
But more important - there is no shorwall.lwp yet!
And given the degree of complexity there may never be :-(
I personally liked the documentation within the config files, as they
provided
13 matches
Mail list logo
