Tux Takes A (Tasmanian) Vacation
One would be hard pressed to find a Linux user who hasn't at one point or another become acquainted with Tux, the fine-flippered fellow who serves as mascot for all things Linux. Everybody needs a break now and again, though, and so Tux has gone on sabbatical — reportedly to work as a barber — leaving the face of a very worthy cause to hold down the fort.
Many in the Linux community will be familiar with the story of how Tux came to be the Linux mascot. Linus Torvalds, creator and developer-in-chief of the Linux kernel, reportedly has a "fixation for flightless, fat waterfowl" that led to the choice of a penguin, though there are a few explanations of how he came to be such a fan. Perhaps best known among them is Linus' claim that he was savaged by a killer penguin during a visit to Australia — an anecdote he shared with Linux Journal way back in 1995 — and from which he may or may not have contracted a rare condition known as penguinitis, said to cause one to "stay awake at nights just thinking about penguins and feeling great love towards them."
What the community is less likely to be familiar with — and the reason for Tux's vacation — is the horrific infectious facial cancer that threatens to render Australia's Tasmanian Devil extinct. In an effort to raise awareness of the Tasmanian Devil's plight, Tuz — the Tasmanian Devil-cum-penguin logo from the 2009 linux.conf.au held in Hobart, Tasmania — is standing in for Tux for the 2.6.29 Linux kernel cycle.
This is only the latest effort on the part of the Linux community to aide the ailing Devils. During linux.conf.au's Penguin Dinner, over $40,000 was raised for the cause, including a $25,000 pledge that resulted in Linus personally shaving off the beard that had adorned the face of Bdale Garbee, HP's Linux CTO, for over 27 years.
During the three months of this kernel cycle — and after it as well — the Linux community is encouraged to learn a little about this endangered species, help raise awareness about the threat to the Tasmanian Devil, and — where possible — contribute to the cause, so those who come after us will have the opportunity to see the Tasmanian Devil somewhere other than the extinct section of their science books.
Tuz is a "penguin" with a cause - are you?
Justin Ryan is a Contributing Editor for Linux Journal.
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
- Tech Tip: Really Simple HTTP Server with Python
- Returning Values from Bash Functions
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
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