I'd like to thank Charles Curley and (obviously) Linux Journal for writing the “Emacs: the Free Software IDE” article in the June 2002 issue. I've been using XEmacs for four years for my programming projects, and Charles' article opened my eyes to a bunch of options I wasn't even aware of. I guess I'll be spending the next couple of weeks (or months) going through the Emacs documentation to see what else is lurking in the 20MB of source code. Thank you LJ for publishing such an informative (and well-written) article.
—Robert James Kaes
It's great that you can afford to spend an entire page on humor, even though it's not the April issue. And it's even that dry, sarcastic humor that you usually find only in British publications. I'm referring, of course, to the Compaq ad parody on page 51 of your June 2002 issue, where they brag about being such an early adopter of Linux when “their” employee, a Mr. Jon “maddog” Hall, ported Linux to “their” Alpha system. And how “they” funded and otherwise supported Linus as early as 1994.
As a matter of fact, wasn't Mr. Hall employed by DEC in 1994, when he ported Linux and helped to get funding for Linus to support the Alpha architecture? In 1994, wasn't Compaq, as well as Dell and all the other major OEMs, claiming that no one wanted a Linux system?
I realize that Compaq now owns all the assets of DEC and that marketing people have no shame, but if this ad is believable, perhaps I should be able to buy a Picasso and then claim that I painted it.
Jon “maddog” Hall replies: Linux Journal was kind enough to allow me to answer your Letter to the Editor.
No one felt worse about the demise of Digital Equipment Corporation and its purchase by Compaq than I did. I had used DEC products since 1969, and it was on a PDP-8 through the use of a DEC training manual that I taught myself assembly language programming. When I was the Department Head of Data Processing at Hartford State Technical College, DEC repaired my PDP-11/70 for free because it had taken them so long to find the problem, and the school had no budget that year for the “time and materials” it would have taken to fix it. Later I learned UNIX and was system administrator to six VAX 11/780 machines at Bell Laboratories.
Through the years I got to know a lot about DEC culture and its commitment to its customers. As part of this commitment I was involved with DECUS, and from the DECUS members (Kurt Reisler, in particular) learned about Linux. Digital Equipment Corporation was more than a company, it was a family.
Yes, I was working for Digital at the time that the Alpha Project was started. Yes, it was several years before Compaq bought Digital. Yes, I felt a pang as Compaq took over Digital's role as the “first system vendor to join Linux International” (even before VA).
On the other hand, to deny Compaq the right to that claim denies the work that the people who still are employed by Compaq (or should I say HP?) did at that time. I know that Maurice Marks, who basically funded the Alpha Linux work in the first days is still at the “new HP”. Jay Estabrook (Hi Jay!) who did a lot of the low-level porting work is also still there, helping to continue support of the Alpha with Linux. The Alpha high-performance group, who started some of the first commercially available Beowulf clusters is still working away. The Digital compiler group, who ported their compiler technology to Alpha Linux is still (to my knowledge) working away. There were many, many people besides me who contributed their time and expertise, paid and unpaid, employee and customer, to the Alpha Linux Project. They did it because of the love of Linux and the love of Digital. They did it both with the support of their upper management and sometimes in spite of it.
To deny them their role in the support of Linux just because their company now has a new name is not fair either.
And if Compaq does not claim the right to say that they supported Linux first, who does? Digital Equipment Corporation is no more, and all the wishing to bring it back will not make a bit of difference. Soon I will expect to see Hewlett-Packard take up the mantle. And now, to set the record straight, a lot of other companies had people supporting Linux early on. Sun supported David Miller to do Linux porting work to Sparc. Compaq had people in Houston who helped to write device drivers and do porting. I know there were people at IBM and HP who were also doing Linux work. But for one reason or another the cultures of their companies did not allow them to have the visibility that Digital's culture allowed me.
In 1998, when a lot of companies held up their hands to say “they supported Linux” a lot of people were able to come “out of the closet”, but that does not mean those people were not active before. I had just come out a little sooner, and with a little more fanfare. Then again, I have never been a shrinking violet.
The world of computer company buyouts and mergers creates little tricks in time and space, and we should learn to live with them. A friend of mine, David Mosberger, who did a lot of work on Alpha Linux, recently wanted to return an Alpha system lent to him by Digital in 1995. But he did not know who to return it to, since Digital no longer existed. I told him to just hold on to it, and that things will be made right again. You see, for the last several years David has worked for Hewlett-Packard. His system is back home again.
The bottom line of this is that if I were writing a history book, I would mention the contributions of Wang, Prime and a host of other defunct computer companies like Digital Equipment Corporation. But I live in the here and now, so the current company that supported Linux in 1994 is Hewlett (née Compaq, née DEC) Packard.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
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.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- 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