login
Search
Today Oskar Andreasson has released version 1.1.0 of his iptables-tutorial package, a series of documents explaining netfilter to the layperson. He mentions quite clearly that he would appreciate it if netfilter coders/experts would "if possible, please have a closer look at the tutorial."
The tutorial can be downloaded at
http://www.boingworld.com/workshops/linux/iptables-tutorial
Below is the full e-mail message.
From: Oskar Andreasson
To: netfilter-devel AT lists.samba.org, netfilter AT lists.samba.org
Subject: [release-update] iptables tutorial 1.1.10
Date: Fri, 12 Apr 2002 14:43:41 +0200
Hi all again,
This is an early warning that version 1.1.10 is about to be released of the
iptables tutorial. Most old bugs and problems have been worked out and fixed
except for a small set of persistent problems (double hyphens being quashed into a
single one, etcetera). I have been working on them, and I hope to fix them until
version 1.1.11 of the tutorial, which will hopefully be the last version for a
few months forward, except smaller version changes which will happen if I get
bugreports or problem reports from people.
Before I say anything else, I would like to ask any netfilter coders/experts
to, if possible, please have a closer look at the tutorial. I need technical
feedback really bad. I am more or less blind to any problems within it right now,
and it would be tremendously appreciated if any of you could have a closer look
and report all/any bugs you find in it. I am sure there must be at least one
error per written line :-).
For those who do not know, I will stop writing this tutorial for a brief period
of time since I have heaps of other projects who are waiting in line to be
finished. I will continue to maintain this tutorial in the meantime, but not as
extensively, and there will most probably not be any large additions for the next
5-6 months or so.
Due to recent events where certain spam robots have harvested this site for
e-mail addresses I have chosen to write all e-mail addresses, except my own, in a
harsher to harvest form. For all those of you who have gotten directed spam
about "your site at boingworld.com...", I am sorry for any inconvenience this may
have caused and I hope you don't have any hard feelings about it. I have sent
"cease and decist" mails to these spammers since what they have done is illegal
according to local laws where I live but I suppose this will make no difference
at all, as usual. If you can find any e-mail addresses that are still not
rewritten, please send me a report about it.
The tutorial should look more or less good now imnsho. If you find any parts
that are unclear, please send me a report about it.
Have a nice day,
Oskar Andreasson
http://www.boingworld.com
http://people.unix-fu.org/andreasson/
mailto: blueflux AT koffein.net
PS. Sorry for the cross posting, I wanted to reach all of you netfilter
developers as well. DS.
Submission Voting Extension
What about extending voting so that if a timeout occurs and a minimum vote-count (less than the normal vote-count) is reached, the submission is posted?
The point is that sometimes submissions lie in here for days maybe one or two weeks. In the end the submission is already deprecated.
Awaiting your comments, especially what Jeremy thinks about it?
--
I used to have a sig until the great Kahuna of FOOness
told me to dump it and use /dev/urandom instead.
Re: Submission Voting Extension
The queue is currently performing as I'd hoped... It allows all members to see current submissions, and vote whether or not the story should be posted. This gives me a little more insight into reader opinions.
If I read a story in the queue that I want posted, I'll typically bump it out of the queue to be posted immediately, once I've read through it, edited for grammer, formatting and sometimes content.
If I read a story I don't want posted, I'll typically vote against it and leave it in the queue. Usually the choice is obvious, and the story gets dumped. However, sometimes it lingers, as votes given are split. That comments are hidden until after a person has placed his/her vote contributes to these lingering stories - that's something I need to fix.