Subj : Re: IP Chains To : Willowolf From : Sniper Date : Wed Oct 27 2004 12:55 am -=> Willowolf wrote to Angus Mcleod <=- Wi> Re: IP Chains Wi> By: Angus Mcleod to Willowolf on Fri Jul 30 2004 11:14 pm > > Wow, now I have no idea which to choose... ;) > > What exactly do you want to do, and what is your skill level? I like > Slackware, but you might be more comfortable with something else, depending > past experience and future needs. Wi> I have been using Debian Linux v3.1 (Sarge) as the OS for my Wi> firewall box for a while now mainly because I like the way it handles Wi> package management with apt-get and dpkg. Oh oh... can't I interject some info here? :) Wi> The first Linux distro I installed was Slackware 3. and that was a Wi> couple years back. I didn't do much with it being that I didn't know Wi> much about it at the time. many years back, yeap, started with Slackware Kernel 1.12. Been througt alot with it myself. :) Wi> Even though I was able to install and configure Debian with Wi> IPTables and set up a decient firewall there is still very much about Wi> Linux that I need to learn. Sometimes I think I should have chosen a Wi> distro that isn't so easy to install packages with. The apt-get Wi> feature really makes it easy, a little too easy for someone who wants Wi> to learn the OS, not just have it work. Downloading software for Wi> Debian is real simple as long as there is a deb package for it. I need Wi> to learn how to download source and compile it with Linux. I've done Wi> it once or twice, but I followed the installation instructions that Wi> came with the source. Learning vi or emacs would be nice. I've been Wi> using pico because it's the easiest for me to use and navigate around Wi> in a text file with while I'm making changes to configuration files. There's no need to worry, you can still compile and install files, as on any other distro... sometimes easier, and with more understanding. The reason I say this, is because when you did your original install, you probably didn't install all the packages that your new program needs, so, you have to read the stop errors and figure out whats needed... either get the .deb or find another install, compile it, install it and try again. I've gone through this line 4/5 times... :) Wi> As someone who has been using Linux for quite some time, what Wi> would you recommend to someone with my skill level (pc technician for Wi> 12 years, network admin for 4 years on Windows) that would really like Wi> to learn Linux? In your situation... I have one thought... stop running windows. Or as I have, my primary machine is my Debian Linux machines. I use my Windows boxes for one or 2 purposes, and only because I have yet to find a replacement for the programs I run on them. But everything else I do, I do with the Linux machines. This "Forces" you to do it. No more playing around with it. Use it. Wi> I can see the benifits of the Linux OS and the amount of control Wi> and power the OS has. Running servers off of it is a lot cheaper than Wi> purchasing a license from M$ to run one. I have converted a number of my clients over... The only ones left were specifically needing features from Exchange Server. As I have not found a quality Linux replacement for that , I am not converting them. But the rest... oh yes... and they love the savings... hell, even their server's price is drasticaly reduced because they no longer need this monster machine... I can get a few replacement parts, fix up there old server, install Debian Linux and we are in business. :) .... No new century began yesterday. NY TIMES editorial, 1/1/1900 --- MultiMail/Linux v0.45 þ Synchronet þ Killed In Action BBS Telnet://kia.zapto.org .