search for: rshannon

At Tom Eastep''s request, an informal Shorewall Documentation Support = Group (DSG) is hoping to relieve some of the writing and editing burdens = that come with maintaining and improving the Shorewall documentation. = The DSG welcomes and needs your suggestions and contributions about all = aspects of the documentation, including structure, content, references, = style, grammar --

Perhaps Drupal''s most powerful and versatile feature is its taxonomy -- essentially the core metadata used to describe, organize and manage content -- important stuff for a good Drupal-based site. Please read http://devel.shorewall.net/node/25, and add any suggestions you might have about how the devel site''s metadata could/should be designed. Ron

A phpMyFAQ demo is available at: http://devel.shorewall.net/node/26 Just one possibility, only a default install & UI, but working. This app has a lot of functionality, including interactive Q&A inputs, and XML and PDF outputs. Please check it out, and don''t forget to leave review comments on the site. Thanks. Ron

As one of those who volunteered to help on this, I apologize to you and = the rest for being slow. Ironically, as this message arrives, I am in = the process of loading 1.3.1 and recording my edit ideas for the QSG = step-by-step... so there may be hope yet. I hope to have the compilation of recent suggestions done by Wednesday. > -----Original Message----- > From: Tom Eastep

We''re starting to collect several comments for doc revisions, which is = great. Another existing source of comments and suggestions is the list = archives. Would someone be willing to spend an hour or two to (1) search = the list archives for documentation issues/suggestions, perhaps using = search terms like: docs, documentation, instructions, Quick Start, = samples, etc., and (2)

Tom, Thanks for all your hard work on this project. I will also volunteer to = help co-ordinate the Quick Start Guide, Samples and/or other = documentation efforts. If you have suggestions or "to-do" lists, they = would be helpful, of course. Steve H. (and interested others): we should probably keep further doc = support conversations off the announce list, probably just on the devel

More than one of our docs issues revolve around some confusion between "IP masquerading" and "SNAT" -- a confusion I might share, or if contagious, I may be catching. <g> I think of SNAT more or less as a special case of IP masquerading, applicable when, for example, the external interface has multiple IP''s and you choose to _explicitly_ set the address through

IMHO, our big picture challenge is that multiple explanations for several topics are spread out over several different docs and pages One parameter is frequently discussed in four or more places (QSG, files reference pages, file comments, main documentation, etc.) That gives multiple perspectives, which can be good, but can also lead to at least the appearance, especially to a beginner, of

In a previous thread, Tom listed advantages (reproduced below) of Proxy ARP over NAT. They are great reasons, but I have one reservation. By using private addresses with NAT for servers in my DMZ, I can granularly allow specific traffic, such as to/from the SMTP gateway/relay in the DMZ, to connect inbound from the DMZ to an internal (LOC) mail server, and know that it comes only from a

Attached is file "QSG-issues-1.0.txt" containing a numbered and commented list of issues collected from contributors and recent lists activity. It might be cool to have these issues in some spiffy issue tracking system like RT or something, but for a low tech start it''ll probably suffice. COMMENTS - IMHO (no particular order): I have searched the archives for additional