An open letter to Adobe
Hello, oh great and powerful Adobe people.
Thank you so much for releasing Flash Player 10 beta 2 for Linux. Thanks even more for (finally) building in support for video4linux2 Webcam technology. You have no idea how much we appreciate that. The only problem is that many (if not most) of us can't use it. You see, it crashes our browsers within seconds.
Reading earlier posts on this subject, it's obvious that Adobe is aware of this problem (Flash player 10 beta 2 crashing Firefox) and that they have fixed it in-house. I think I speak for more than just myself when I say, "Please, just let us have the fixed version." You don't know how long we've waited for video4linux2 support. The suspense is killing us. Besides, it's kind of rough to be told that a beta is available with said features, then not have it work. It's even harder when we are told it's fixed by we can't possibly have it. So, please. Please. Let us have the current fixed version. We know it's not the real, final product, but we accept that. It's cool. Really. What do you say? Come on, guys. One little tiny fixed beta? No one is going to complain. In fact, we'll say nothing but nice things about you. Really.
What do you say?
Please. Pretty please . . .
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!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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