Domain: filewatcher.org
Stories and comments across the archive that link to filewatcher.org.
Comments · 8
-
Re:Clear this up for me
A trip to google leads me to believe that it has something to do with ham radio. This site seems to explain what's going on, but I'll be damned if I can decode exactly what it's talking about.
-
try http://netfilter.filewatcher.org/It is really easy.
iptables -L will list the tables in the default chain. Then there is iptables -L -t nat and iptables -l -t mangle
The best guide I found was http://netfilter.filewatcher.org/unreliable-guide
s /packet-filtering-HOWTO/index.htmlThis explains how packet travers the filters which I though was easier than ipchains to learn. It also talks about using the ipchains module in 2.4 which means you can upgrade you kernel and keep your old firewall rules. It also goes over some of the basic options. This guide is mainly geared for using ip masquarading or now know as nat, but it is a great place to start. Also pick up a copy of last months Linux journal as they had an article on iptables.
However I must warn you that once you go to iptables you may find it difficult to want to ever think of ipchains again. I know I do.
-
Re:DOS Software
Friend, have a look here: http://filewatcher.org/sec/qb2c/int_year.html.
Drop that QBasic into C, build it up on Linux, and welcome to the present.
-
Re:Simple breakdown
and for perl:
perl -MCPAN -e install :
suck source accross the net, resolve dependencies, buils, installs...
ok, that's only for perl, but that's great, when it works ;-)
anyway i don't really see in what port system, apt get, rpm or whatever have to do with .NET. I thought .NET was dealing more with services (passport stuff, and some C# bullshit progs around -maybe other languages too-), than with apps, that are most of the time simply useable on any UNIX-like system (./configure,make,make install works on most recent progs out here, on ever GNU/Linux distro, most *BSD, and probably MacOS X too, and thus usually binaries packages exist as well) so what's the point of this article ? As far as apps are concerned, i don't see why we would use *BSD ports, that seems very odd to me, and instead i think it would be far better if things were cleared up for everyone about where to install all the stuff from a prog (/usr ? /usr/share ? /usr/local ? /var ???) i've seen in the past years that much funny things about that. see for apache, in the past default content directories were under /home/httpd, now it is in /var/www (using RedHat), and it's probably different on another distro. That makes no sense to me. it's silly. I think LSB 1.0 is far better news than that port thing we don't care.... (well, FHS seems to be still working on, but it's about ending with a stable version, despite i don't find clear enough the difference between /usr and /opt)
but maybe i'm only completely missing the point about that non-event... -
Re:Solutions to Today's "Ask Slashdot?"
-
Mirror links
-
Urlview
ever heard of urlview? It pops up a window after parsing some text (or an email message) displaying all that url-like items. You simply click a key and it loads your favorite browser with the url.
I couldn't find a link to urlview's homepage, but you can find info about it in Mutt's manual or at filewatcher
-
Freshmeat not irreplacible.True words, throughout.
As for alternatives to Freshmeat, try Filewatcher.
Daniel "Nixon" Mikkelsen, spam@fix.no