As we zero in on the second “production” release of the Linux kernel, 1.2, the most common complaint I hear about Linux is its lack of documentation. But, is that really a problem? I think not. Here's why.
What this means is that if you are looking for a book on basic Linux commands or how to use the VI editor you have a lot of choices. When you go shopping you just have to say Linux every time you see Unix. Sure, there are some differences, but not many from the user's point of view. As all “Unix-like” systems converge on the various standards, such as POSIX and Spec 1170, the differences disappear. Today there are more differences between a BSD-based version of Unix and a System V-based version of Unix than there are between either of these and Linux.
There is real Linux-specific documentation. The Linux Documentation Project (LDP), headed by Matt Welsh, is producing high-quality documentation. Right now, Matt's own Linux Installation and Getting Started is either included with most CD-ROM distributions or available from the distributor or reseller.
Olaf Kirch's Linux Network Administrator's Guide has been published by SSC and an O'Reilly version is also on the way. The excellent coverage of networking in general will probably make this book the first Linux-specific book to become commonly used by non-Linux (read that as Unix) users as well.
Michael K. Johnson, our editor, is now in the process of updating his Linux Kernel Hacker's Guide (KHG). You will see some of this information in his new monthly Kernel Korner column. And, once it is up to date, SSC plans to publish it.
There are more LDP books on the way. Expect to see a System Administrator's Guide, Programmer's Guide, User's Guide and man pages. And, of course, all of these books are available on the archive CD-ROMs and ftp sites.
Besides the LDP efforts, publishers are getting on the Linux bandwagon. Springer-Verlag has published a book titled Linux: Unleashing the Workstation in Your PC, available in both German and English. O'Reilly is working on a Linux book, and rumors indicate that Benjamin-Cummings and SAMS are working on Linux books. 1995 will probably be the year of Linux documentation.
Many people who are complaining just downloaded Linux off an ftp site or bought an archive CD. In either case, there is lots of documentation available but it doesn't print itself. You need to remember that if you bought SCO Unix you probably dug into your pocket for $1,000 or more as opposed to less than $100 for Linux. Either take some money and buy the books you need or take some time and print out what is on the CD.
The other problem, of course, is getting you to read the documentation. Many CD vendors are now including a small book with the distribution to get you started. People seem less intimidated by a 20-page insert in the CD case than by a 1,000-page manual. Just remember, you may still need that 1,000 pages of documentation to find all the answers.
Yes, there is. Linux is changing so rapidly that it is hard for the documentation to keep up. For example, if you buy a printed copy of the Linux HOWTOs that has been sitting on a bookstore shelf for a few months, most of it is already out of date. Documentation that will be outdated by the time it is printed is not what publishers (or booksellers) like.
But this is one of the reasons the LDP separated the HOWTOs from the LDP books. These books evolved with much feedback from the early users and, as each one becomes stable, they are becoming available in printed form.
Many of the distributors include HOWTOs on their distribution CDs along with browser tools to search, read and print them. The initial focus has been browsers under MS-Windows. (As much as I dislike this dependence on Microsoft, some people are going to need to be able to read the documentation in order to get Linux up and running.)
Matt Welsh, coordinator of the LDP, has recently made the HOWTOs available on sunsite.unc.edu in HTML format (as well as other formats). This means that if you have the HTML format documents in an uncompressed form on your system (some archive CDs have this) you can use a WWW browser such as Lynx or Mosaic to access these documents in hypertext form. And, as the lead time on pressing and distributing a CD is shorter than that for a printed book, the consumer can get the best of both worlds—stable documentation for their bookshelf and up-to-the-minute documentation on the CD.
In conclusion, the Linux community and the publishing community have heard you and are taking action. There is documentation and there will be more. But remember your obligation: support these publishing efforts including the LDP, get the documentation and, last but not least, RTFM.
Phil Hughes is the publisher of Linux Journal.
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!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 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