When people first start looking at Linux there are some hurdles. The first one is understanding that Linux is free. Because so much software is licensed, the idea that you can get a copy and legally give it to all your friends and use it on all your computers seems to take some getting used to.
Once people get over that hurdle, the next problem seems to be “which distribution should I get?”. This is because there isn't just one Linux—a concept that is familiar to many Unix system users but fairly foreign to the MS-DOS or MS-Windows user. This article addresses that question. Hopefully the third question, where do I get it, can be answered by our advertisers.
Historically, the word Linux had a somewhat different meaning. It was really just the operating system kernel. People would then collect various pieces of software (a compiler from one place, login code from another and so on) and put together their own system. The problem is that this took a lot of time, and as the amount of support software available grew the choices grew as well.
The solution was for someone to make a distribution, a collection of software consisting of the kernel and all the support programs that a user would need. What happened is that more than one “someone” did this because of differing needs. And each of these distributions was called “Linux”.
What's wrong with calling them Linux? Nothing, if we can avoid the confusion that it initially introduces. The confusion comes from two areas:
Different distributions contain different programs.
Linux is really the kernel. When we lump all the other programs in and still call the contents Linux we are ignoring the work of others including FSF for the C compiler and most of the utilities, and the University of California at Berkeley for Ingres and Postgres.
I am sure the label Linux will stick, but I do think it is important that we recognize that there's a lot more to what we get in a distribution than code written by those who would be considered Linux developers.
Now, on to distributions. This isn't intended to be a complete list, just a quick look for beginners. I encourage anyone with a different distribution that they consider important to write to us and tell us about it.
The first complete Linux distribution was SLS. Although the most recent release is sorely out of date today, I mention it for historical reasons. Many people who are using Linux started with this distribution, which was produced by Peter MacDonald. It also offered the basis for other distributions like Slackware.
Developed at the University of Manchester, MCC was designed to be quickly installed by anyone. It has excellent documentation and is both compact and very stable. MCC was designed to be installed on 386 systems in a lab used by computer science students. It includes networking via ethernet and a complete development system but lacks such things as print spooling, uucp and X windows. Because of its excellent documentation and compact size (easily fits in 30MB of hard disk space; distribution is 8 floppies) it is a great place to start-particularly if you have little or no Unix experience.
At the time of this writing (February, 1994), the MCC distribution is based on a rather old kernel. It is, however, very stable and well tested.
Slackware evolved from the ideas behind SLS, a complete Linux system with an installation system that makes it possible to pick and choose what you want. It isn't perfect but it is very current, well supported and very reliable. The imperfections are generally in terms of a missing link or wrong permission. Here at Linux Journal we have two systems running Slackware, and the only serious problem we encountered was with smail. After talking to other Unix users we determined that the problem was actually an smail bug, not a Linux bug. We replaced smail with sendmail+IDA and all seems to be fine now. Some distributors (such as Trans-Ameritech) are distributing Slackware on CD-ROM.
Available only on CD-ROM, this is a very popular distribution. Current and complete, it offers a quick way to get a working system up and running. It includes X-windows (in fact, it requires you to load X to do system configuration) and a pretty amazing set of tools. Like most of the up-to-date distributions, it has a few bugs. It is, however, a great choice for someone who wants to get a working Linux system with X up and running quickly. I also feel it is well worth the $50 for the amount of source code you get in a compact form. We have one Linux system in the office running Yggdrasil.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide