similar to: Shorewall development web site

Hello, I have the go ahead to fix documentation. For starters I will clean all extraneous crap from the markup. Then fix any errors and typos. If anyone sees any gramatical errors or typos or needed clarifications or expansions or whatever, please post them here. Or additional FAQ entries, etc, all will be considered. I hope to keep most of this conversation on the shorewall-devel list. Any

Good Morning Mike, I''m finding that when I load a document, XXE is blindly removing all "superfluous" white space from "programlisting" elements. This of course is leading to a real mess (check out the FAQ on the web site :-( ). What can I do to avoid this? -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \

Attached please find updated build and publish scripts. They set the ''ulink.target'' parameter appropriately when converting docbook->HTML. I have always hacked my xhtml/params.xsl file to set this parameter; these updated scripts make that abomination unnecessary. Paul/Mike: It might be a good idea to add a CVS project for these scripts. -Tom -- Tom Eastep \ Nothing is

Everyone, Progress was slow today. I started out well, but then I ran into Documentation.htm. Progress slowed considerably, as I analyzed the document structure. I''m up to /etc/shorewall/hosts Configuration. I hope to finish Documentation.xml by tomorrow evening. Converted documents: 6to4.xml CorpNetwork.xml FAQ.xml Please post feedback, if you see any problems with the converted

Of the remaining HTML files in the Shorewall-docs/ project, the only ones that I want to convert to HTML are: standalone.htm two-interface.htm three-interface.htm Paul -- while file(s) are you working on? -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Hiya, > Ok with me -- if I get too frustrated with DocBook, I''ll just start > editing the HTML again. > > -Tom > Well the fact that VIM is supported by Docbook is a plus .. But I still think the Wiki idea is well .. Lets get the doc at a CVS and Docbook stage .. Walking before running .. plz plz .. Francesca PS: I have thrown Windoze out the Window here (Pardon The

Hello, In reference to http://wiki.rettc.com/wiki.phtml?title=Wiki_Shorewall_FAQ ; Well, after a lot of emails I setup a wiki for shorewall, etc. It has proved to be completely useless. I have noticed one slight distro specific example added, a couple typo additions and fixes, otherwise, all contributions have been in excess (Tom...), or in malign. For my uses it has proven of little use as

I''ll take this one next. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Hello, I leave for a couple days .. (Well months) and look at what has happened. :-) I would throw my support in behind Xoops .. to be honest .. If a portal is what we are trying to achieve here. I just happen to think that sometimes .. More work goes into web design etc than goes into actual Code. But thats because I am a lamer at web design :-) I am coming in here a bit late .. But tell

Hello, I have a naked mediawiki running, from http://wikipedia.sourceforge.net/ The wiki is here: http://wiki.rettc.com Let me know what you think, and if it will be suitable for populating with FAQ stuffs. Alex http://www.rettc.com

I''m working on shorewall_setup_guide.htm -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Hi folks, I''m conducting a straw poll for your opinions on whether we should send CVS commit logs (probably with diffs) to the shorewall-devel list, or to another (new) list? I can see advantages to both ways: separate lists mean that people who aren''t contributing code don''t get flooded with code noise, but a single list will help keep everyone involved in the

I''m beginning to think again about what will be different in 2.0. Here are some thoughts. a) User-defined actions will be emphasized. - A library of actions will be available with names such as: AcceptSSH AcceptDNS DropWindows (drops all SMB noise) DropBroadcasts (Silently drop all Broadcast traffic) ... The possibilities are nearly endless but should

Tom, Can you/someone get a news feed setup for shorewall announcements? If not, I''ll have to make use of the shorewall rss feeds at SF. Project RSS Feeds: shorewall http://sourceforge.net/export/rss2_project.php?group_id=22587 BTW, planetplanet.org has links to some cool feeds. -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net

Hello Mike, Tom, (I am not sure who is working on this part) There are some funny characters in FAQ.htm in a number of places. I have provided a precursory analysis of this issue. It is not a big=20 deal, but something that I imagine will be worked out at some point. I have provided a couple examples. Is there a way I can see the xslt stylesheets? Could they live in cvs at some point? Maybe I

Hello, Mike Noyes and myself have populated http://wiki.rettc.com with the shorewall FAQ. This wiki is running MediaWiki, http://www.mediawiki.org. Currently, a couple items are not complete. I have just begun a heavy semester of mathematics/physics studies, and do not have much time to give to this. But, it is online, and seems to be stable. I will keep an eye out for abuse, and limit

It has been asserted that the use of CVS for maintaining the Shorewall documentation has been a barrier to community participation. To test this theory, Alex Martin has created a Wiki (http://wiki.rettc.com/wiki.phtml?title=Wiki_Shorewall_FAQ) and with the help of Mike Noyes Alex has populated the Wiki with the Shorewall FAQ. Feedback is welcome. -Tom -- Tom Eastep \ Nothing is foolproof to a

It is with regret that I announce that Shorewall development and support is officially ended. Sean''s post has finally driven it home to me that in the long term, trying to support a project like Shorewall is impossible for a person of my personality and age. Sean -- please believe that this isn''t about you or your post -- your post was just the proverbial straw on this old

Greetings, What programming languages besides shell scripting are used in shorewall? What knowledge is needed to help in shorewall development? I figure iptables is a goood bet but is there anything else as well? Thank you for your time. Regards, Jason

Hi folks, Over the weekend Ron has made some good progress with functionality available at http://devel.shorewall.net, and i''ve converted all of the content i had placed at http://shorewall.dyndns.org (which is now a redirect to the former). Please have a look around and give your feedback, either here or on the site itself. -- Paul <http://paulgear.webhop.net> -- Did you know?