On Sat, 2006-11-25 at 08:56, Tom Eastep wrote:
> Mike Noyes wrote:
> > 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 wil
Mike Noyes wrote:
> 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
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
>> p
KP Kirchdoerfer wrote:
> Am Donnerstag, 23. November 2006 16:16 schrieb Erich Titl:
>
> Hi Erich;
>
>> 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
>
Am Donnerstag, 23. November 2006 16:16 schrieb Erich Titl:
Hi Erich;
> 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
Am Donnerstag, 23. November 2006 19:42 schrieb Mike Noyes:
> 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, cre
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
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 wo
d from the files and
will be replaced by manpages. This presents a problem for users of
embedded distributions like Bering-uClibc who typically don't have
access to manpages."
Eric
>
> -Forwarded Message-
> From: Tom Eastep <[EMAIL PROTECTED]>
> To: Eric Spakman <[
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
Or am I missing something? ;-)
Eric,
Ah. We are in agreement then, or I think so. Do you still plan on a
"shordoc" package?
The post by Tom to you made me believe Shorewall man pages were
available for current Bering-uClibc releases.
-Forwarded Message-
From: Tom Eastep &l
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 th
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 s
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.
>>>
>>>
>>>
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 shi
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.
>
>
There is no shor
On Wed, 2006-11-22 at 16:56, Paul Traina wrote:
> Mike Noyes wrote:
> > On Wed, 2006-11-22 at 14:50, Paul Traina wrote:
> >> Mike Noyes wrote:
> >>> I believe, an even better solution is using DocBook XInclude from LEAF
> >>> to the Shorewall site. This is only possible if you're using DocBook XML
On Wed, 2006-11-22 at 14:50, Paul Traina wrote:
> Mike Noyes wrote:
> > I believe, an even better solution is using DocBook XInclude from LEAF
> > to the Shorewall site. This is only possible if you're using DocBook XML
> > to generate man pages, and the docbook xml source is
> > available via uri
Mike Noyes wrote:
> I believe, an even better solution is using DocBook XInclude from LEAF
> to the Shorewall site. This is only possible if you're using DocBook XML
> to generate man pages, and the docbook xml source is
> available via uri.
>
The only problem with that idea that I can think of,
On Wed, 2006-11-22 at 14:39, Mike Noyes wrote:
> On Wed, 2006-11-22 at 09:10, Paul Traina wrote:
> > Mike Noyes wrote:
> > > On Mon, 2006-11-20 at 11:30, Mike Noyes wrote:
> > >> We have a location in cvs for man pages, and output them daily for our
> > >> documentation build. All someone needs to
On Wed, 2006-11-22 at 09:09, Paul Traina wrote:
> Mike Noyes wrote:
> > On Mon, 2006-11-20 at 10:22, Tom Eastep wrote:
> >> The documentation contained in Shorewall configuration files has always
> >> presented an upgrade dilema for users: "Do I spend time merging the new
> >> documentation or do I
On Wed, 2006-11-22 at 09:10, Paul Traina wrote:
> Mike Noyes wrote:
> > On Mon, 2006-11-20 at 11:30, Mike Noyes wrote:
> >> We have a location in cvs for man pages, and output them daily for our
> >> documentation build. All someone needs to do is add them to our
> >> repository.
> >>
> >> http://l
22 matches
Mail list logo
