Just Folks
Who did what concerning Linux 1.0, and who's who in open systems, are intriguing queries. Not merely because I think “open” goes back 45 years, but also because I'm not at all certain that any of today's contemporaries (other than Linus, Guido, Larry and Eric) will be considered important in a decade. While Dennis Ritchie and Ken Thompson are remembered, other influential people have faded into the mists of time.
This isn't meant to dismiss the activities of, say, Jon “maddog” Hall. But who remembers the “gang of five” who started USENIX? Who recalls that Lou Katz, then at Columbia University, was the first President? Or that Katz and Reidar Bornholdt organized the very first UNIX Users Group meeting (May 15, 1974, in the Merritt Conference Room at Columbia's College of Physicians and Surgeons)?
Nor do I want to devalue Tim Berners-Lee's contribution. But Peter Deutsch's archie has vanished, as have gopher, veronica, jughead and Mosaic.
We talk about “Internet time”, but our memory of individuals is even worse than our memory of things. So I thought I'd put together a different sort of merit-based who's who—or perhaps a hall of fame for people whose work has had a truly lasting impact. (Note, I intentionally omitted the obvious: Torvalds, Ritchie, Stallman, etc.)
Eric Allman for Sendmail (1978)
John Backus for creating FORTRAN (1957)
Gordon Bell for the PDP-4 through PDP-8 and the VAX
Fernando Corbato for writing CTSS, the Compatible Time-Sharing System (1963)
Edson de Castro for collaborating with Bell
Steve Crocker for inventing the form and writing RFC 1 (1969)
Ralph Griswold for SNOBOL4 (1971) and ICON (1983)
Brian Kernighan for being the “K” in K&R and in AWK
Don Knuth for TeX and The Art of Computer Programming
Mike Lesk for uucp, grep, lex, tbl and refer
J.C.R. Licklider for making the ARPANET possible
John McCarthy for LISP 1.5 (1962)
Doug McIlroy for the idea of pipes
Bob Metcalfe for Ethernet
John Ousterhout for Tcl/Tk
Jon Postel for running IANA
Bjarne Stroustrup for C++
Andy Tanenbaum for MINIX
Larry Wall for rn, patch and Perl
I guess I could easily make this list twice as long. But with very few exceptions, the names would be even less familiar than the ones above.
However, if Backus and his team hadn't developed FORTRAN, we wouldn't have COBOL or Algol or most other languages we use (such as C and PASCAL, both 1971). Without MINIX, we'd have no Linux; without the ARPANET, no Internet.
My real point isn't that everyone ought to memorize who did what to whom. I'm not sure if it matters at all. Alexander Graham Bell, Rudolf Diesel, Tesla and Marconi have their places in technological history, but hardly anyone except historians of science remembers Wankel or even Stephenson. Thus, who's-who volumes are highly ephemeral: some of those once thought important will fade away in a few years. My guess is that we are like those “trunkless legs of stone” in “Ozymandias”.

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Build a Skype Server for Your Home Phone System
- New Products
- Why Python?
- A Topic for Discussion - Open Source Feature-Richness?
- Validate an E-Mail Address with PHP, the Right Way
- Tech Tip: Really Simple HTTP Server with Python
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




1 hour 35 min ago
4 hours 5 min ago
14 hours 7 min ago
18 hours 34 min ago
22 hours 10 min ago
22 hours 43 min ago
1 day 1 hour ago
1 day 1 hour ago
1 day 1 hour ago
1 day 5 hours ago