RIP Dennis Ritchie
It’s a common oldster refrain that when you reach a certain age, you have to get used to people you know dying. I think that we, as a community, will have to accept the fact that over the next decade we’re going to wave goodbye to many of those who were the architects of 70s computer technology.
He died the same month as his contemporary Steve Jobs, but in many ways, he lived on the opposite side of the tech spectrum: Jobs was a great businessman, but Ritchie was a technology man. His contributions to the C programming language and the UNIX operating system are probably the achievements that have had the biggest impact on the world of Linux.
The C programming language was developed by Ritchie in the late 60s. By the mid-70s it had become the language of choice for the system level programmer, offering as it did the advantages of a high-level programming language alongside some of the efficiency of assembly language. It's not as dominant these days because more powerful computers have allowed more complex, and less efficient, languages to become viable choices for application development and even for operating system and driver work. However, it remains, by far, the predominant language in the Linux kernel source code. In addition, the influence of C can be felt in almost all subsequent high-level languages.
The creation of C would have ensured that Ritchie's legacy in computer technology was a substantial one, but he was also one of the main creators of the original UNIX operating system. From UNIX sprang MINIX, a teaching system that inspired Linus to create Linux. BSD, MacOSX and Solaris are other systems that owe their existence to UNIX. Even if not UNIX derivative, all modern operating systems owe something to the influence of UNIX.
Goodbye Mr. Ritchie, and thanks for all of your work in shaping the nerdier side of tech. We'll try to keep our braces closed and our pointers legal.
UK based freelance writer Michael Reed writes about technology, retro computing, geek culture and gender politics.
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
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- 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