2012 LinuxQuestions.org Members Choice AwardsThis forum is for the 2012 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite products of 2012. This is your chance to be heard! Voting ends on February 4th.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Used to be Slackware, but switched to Debian when I installed my new server. Less work to maintain an up-to-date configuration. It just runs in the background and doing an apt-get update/upgrade once in a while is all that's needed.
You're all crazy Scientific Linux easily! RHEL rock-solidity; proper professional documentation from upstream; a genuine will to help from the sysadmins at Fermilab who build it; ten years(!) of free security patches with the ability to stick to the original point install base for that whole period; RPM based (yes I prefer it to dpkg - so shoot me); Sensible packaging & config policy - no unannounced application retirements / replacements, config changes or disappearances or re-naming of config files (Debian devs I'm looking at you). etc..
Should the RHEL clones be combined? While CentOS and Scientific aren't 100% alike, they're pretty much 99.9% alike, so overall any minor differences wouldn't matter.
That said, I think Slackware stands as a good server distribution, with Scientific as a close second. I'm not sure why people seem to think that Slackware package management is still 100% manual. Slackware 14 comes with slackpkg, which will pull in any updates from the Slackware repository based on a changelog file.
RHEL and CentOS are the standards when it comes to Server Deploment...
I agree, but I think all RHEL/CentOS admins should give Scientific a shot. There are both pro's and con's when compared with CentOS, but I like the fact that I have a choice when I need to go to a clone. Of course I prefer RHEL over both, but it's not always an option.