Linus Torvalds at DECUS `94
The Primary Highlight for the Linux/Unix Community was the special appearance of the “Father of Linux”, Linus Torvalds. There were two sessions which featured Linus and both were very informative and entertaining. The sessions were called “An Introduction to Linux” and “Implementation Issues in Linux”. During the sessions, I learned a great deal about the Linux Operating System as well as the promising future of Linux.
According to Linus, there are over 176,000 lines of code in the kernel of which 88,000 lines of code are for device drivers. While Linus is the primary author of the kernel, most of the device driver code has been contributed by others.
The history of Linux may be short compared to the Unix time scale: three years versus twenty-five years. However, much has happened since the beginning of Linux. A few milestones for Linux follow:
From 1991 to the present, Linus has demonstrated tremendous dedication to Linux. For example, the virtual memory code was written in just three days-and it was the three days before Christmas! In three short years, Linux has transformed itself from a very simple terminal emulator to a powerful enhanced Unix operating system. A great deal of work is now being done to further enhance the existing kernel and implement new features. Some of the work in progress involves kernel threads, extended memory management, file system optimizations, and ports to other architectures such as the 68K and the Power PC and maybe even the DEC Alpha.
I had the pleasure of spending an afternoon with Linus in New Orleans, Louisiana and was able to learn a lot about Linus and what his interests are other than the Linux operating system. This was my first chance to meet Linus in person and I was shocked to find that he was not at all the “computer hacker geek” that I dared to imagine. Linus is one of the nicest and most personable people I have ever had the pleasure of spending time with. He has a wonderful sense of humor and is very funny. I found myself laughing non-stop during our chats. Linus lives at home with his family and cats and likes to spend time with his girlfriend. He teaches at the University of Helsinki.
Lately, he has been traveling around the world talking about Linux. Linus jokes that
“if you want to travel around the world and be invited to speak at a lot of different places, just write a Unix operating system.” Upon meeting Linus, one would never dream that he was the author of a Unix operating system; he never brags, boasts or even seems to want very much recognition for his massive effort.
There never seemed to be any selfish attitude at all from Linus. I wish all software developers had the attitude and determination to produce quality code such as Linux and want little, if anything, in return. Someone asked him at DECUS how he felt about other people and companies using part or all the Linux kernel for profit and not giving him any money. Linus simply replied, “I wrote Linux for public use, not for the money.”
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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
- 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