lol!

what about BSD? do they scare you?

BSD sucks. Doesn't like the Linux kernel.

not sure what you mean "do they scare you?" but I've been meaning to install and try out, just haven't had the time and or just lazy. Slackware does the job for me though.

Lets not start any wars kernal...

BSD is more powerful than Linux but it's not quite as user friendly. you can't say it sucks but you can say you don't know how to use it.

Nah, just an opinion

SLACKWARE RULEZ

REDHAT sucks !

Slackware sux
Redhat RULEZ!!!!111

Wow, that achieved a lot.

Let me describe it another way..

Slackware - Elite.

Redhat - Newbies..

Isn't that supposed to be

?

Alright, Stop it or I'll be forced to whip out my Moderator powers and report this post to be closed...

Here's a more useful reply:
RedHat:

1. Uses sophisticated startup scripts that read configuration values from easy to edit and understand config files. These scripts also allow the use of the "service" command, which allows very user-friendly daemon management (e.g. "service httpd status" will check whether Apache is running or not, and "service sendmail restart" will restart the sendmail SMTP daemon.
2. Uses RPM (RedHat Package Manager) to handle installations/uninstallations of different software titles. The RPM philosophy is: ask no questions. Pretty much dummy-proof. All you have to do is run rpm, and your package is installed.
3. Is overall very popular, with many programs available precompiled and optimized for the RedHat Package Manager (RPM) and the RedHat directory tree.

Slackware:

1. Uses simple startup scripts that are more like a bunch of startup commands with their parameters. Slackware startup scripts usually do not use any external config files, as all the options for the daemons are specified (hard-coded) into the init scripts. Due to this, Slackware daemon management becomes slightly more complicated... For example, instead of "server httpd restart", you now have to send a SIGHUP (hangup signal) to the httpd process...
2. Uses simple gzipped tarballs to manage package installations/uninstallations. Provides tools to convert RPM packages to TGZ packages, as well as moderately user-friendly tools to handle TGZ package installations/uninstallations.
3. Is not that popular (I have not seen a single project on SourceForge that provides Slackware TGZ packages).

Verdict:
Slackware is for you, if you don't mind getting your hands dirty. It is a distro for people who enjoy editing startup scripts and files like /etc/passwd directly. It is recommended that you get comfortable with a Linux distro like RedHat and Mandrake before trying out Slackware. Overall, Slackware may sound like an untreated log full of thorns due to its simplicity, but trust me, once you get the hang of it, that simplicity will be more than welcomed by you. To me it feels like a breath of fresh air.

I agree with this, stop acting like kids... Each distro has its own pro's an con's. Arguing which distro is better is futile and pointless.

i tried to install slackware, it did NOT recognize my ethernet card so i had to take it out. why the hell can't any distro of Linux work for me? so far the only to work is Mandrake 8.0 IF you install it about 10 times until it starts to work......that trick didn't work for redhat, it's a shame

what's your card? post your hardware specs