LDP is becoming more popular by the day, and the entire collection was published on paper several times. LSL (now CheapBytes) was the publisher of multiple editions. They were called "The Linux Bible", "Dr. Linux", "Linux Getting Started", "Linux the Complete Reference" and "The Linux Encyclopedia".
By 1997, Guylhem Aznar was appointed coordinator of the LDP. His job was to unify the LDP again: mailing lists and servers were in operation all over the world, and nobody knew who was responsible for what. He started by putting together a staff, a team of volunteers that could give structure to TLDP.
The exact configuration of the core team in those days has been preserved. It was composed of a hub, consisting of one main coordinator, plus individual FAQ, Guide and HOWTO coordinators, Greg Ferguson, Joshua Drake and Tim Bynum, respectively. Furthermore, most translation efforts started in 1994 now are running more or less at full speed, and people have been appointed to manage each translation. One project not listed here, although it was among the first, is the German translation effort. As with the recent joining of some Italian translators, it sometimes takes a while for people find one another.
This team registered the linuxdoc.org domain and moved the entire Linux documentation collection to it, which promptly was mirrored. The relationship with iBiblio (formerly sunsite.UNC.edu) was maintained during the romance with SGI, and the university became a mirror site. The love didn't last, however, and TLDP moved to iBiblio again after the short SGI intermezzo. Paul Jones and his colleagues, responsible for managing TLDP at iBilbio, were very understanding and provided a lot of support, which enabled the centralization of resources in North Carolina.
As far as we could find out, Guylhem and his team also started the discussion and other mailing lists. Prior to that, discussion primarily happened in the Usenet newsgroups. The mailing lists were a good thing; I remember that newsfeed in those days was generating enormous amounts of traffic and consumed--for that time--unreasonable amounts of bandwidth. Some ISPs decided to offer only a partial feed or none at all.
1998 saw the publication of "Linux Undercover", subtitled "Linux Secrets as Revealed by the Linux Documentation Project". Red Hat was the first to use the new just-in-time production method. Previous printed versions often contained stale HOWTOs, but this one essentially was printed straight from the on-line master documents.
In 1999, the project hosted eight guides, including version 1.0 of the Linux Network Administrator's Guide and beta-1 of the Linux User's Guide. These and other documents still were written mostly in SGML or LaTeX.
The first occurrences of DocBook were seen in 2000; DocBook now is the preferred submission format because it enables easy generation of HTML, PS, PDF and other formats from the source files.
Another novelty that came with the 21st century was the creation of a versioning system. Sergiusz Pawlowicz and Gregory Leblanc were responsible for the setup; Sergiusz still manages our CVS. He also became the listmaster by the end of 2000. Up until then, Debian hosted the TLDP mailing lists.
TLDP project was maturing and growing in every possible way. To this end, David S. Lawyer finalized the LDP Manifesto. David is still the point of contact for all license issues.
A new Web site layout was probably the most visible improvement. The new millennium brought the precursor of the site as it is today.
In some documents you still can see references to the old linuxdoc.org domain. The reason for the domain switch was not pretty, unfortunately, but as it is part of the TLDP story, it should be told.
As is so often the case, goodwill and kindness made selfishness rise to the occasion. Many people are interested in TLDP, but not always for the good of the project.
At the time Guylhem was elected president, there was only one other candidate. Guylhem didn't want that man to feel left out, so he trusted him to be the webmaster. TLDP lost the linuxdoc.org domain because the webmaster managed to claim ownership of it. He also purchased the .com domain and ran a commercial Web site on it on the back of TLDP. Needless to say, this caused a lot of friction.
So a new domain had to be found, and tldp.org was short and free. Guylhem took his responsibilities seriously, registered the domain in 2002 and moved the project to the current domain. The team also took this opportunity to broaden the scope of the project, and they combined the move with a restructuring operation that made the project much more efficient.
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|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- 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