"Sorry, but your system does not meet the minimum system requirements"
Sorry, but your system does not meet the minimum system requirements (Adobe). The all-new Yahoo! Mail has not been tested with your operating system (Yahoo).
What do these two messages have in common? In both cases, they were generated by trying to access the service or software from a Linux-based PC. I wish I could say it was because I am running 64-bit Fedora, or because I want to do something special with the sites, but sadly, that is not the case. In the case of Yahoo, I am just trying to access my mail box. It does work, but it "has not been tested," which leads me to believe that if some feature fails to work as I expect it to, I am pretty much out of luck. In the case of Adobe, I need to download something called Adobe Digital Editions in order to read an electronic book from Cisco Press. I guess this indicates that Cisco admins only use Windows or Apple as their desktop systems.
And this bothers me. It bothers me on a number of levels. Linux is no longer just for servers, nor has it been for more than ten years. Major corporations, like Cisco, are pressing for a larger Linux presence, working with development shops and providing software that interacts or runs on Linux.
A web mail client should not have to be "tested" to work with a specific operating system. It should be tested to interoperate with the HTML standards, but the operating system should be irrelevant. That is supposed to be the strength of n-tier systems.
One of the key points I gained from this year's LinuxCon was that the desktop, as a meme, is dead. And by dead, I mean that it does not matter what the hardware or operating system is. It should not matter if you are accessing data via an Android-powered netbook or an Apple-powered tablet. Making the cloud work, means that the standards must be more than hardware and OS. And yet tools that are supposedly designed to make it easier to integrate and interoperate with the cloud and its data are still hamstrung by having to have a specific operating system, bit version, and CPU running underneath them.
As a Linux user, this makes me very angry...and it is time to start expressing my opinion with my wallet. Regrettably, I do not really think that is going to be enough.
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
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- 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