More on Poulsbo (GMA500), Intel, and the Community
I've never done a follow up post on a topic before, but I think this is a topic worth further discussion. Yesterday I posted a rather pointed article focused on Intel and what I consider to be a very poor business decision regarding the GMA500 GPU. There were great comments, and even a responsive post over at Moblinzone.
The opposing argument is that it's not Intel's fault that the GMA500 graphics core is so unsupported in Linux, but that it's the vendor's fault for using the thing in the first place. Oh please.
If I were a factory producing forks, and a hair brush distributor approached me to buy my new 5-tined fork to sell as a comb -- I'd say no. As owner of the Finglehopper Fork Factory, I'm more concerned about the value of my brand than I am about selling my forks to someone who will use my name to misrepresent my product. The GMA500 + the Atom 1.3Ghz CPU was Intel's answer for vendor's demands for lower power, higher performance solutions. That was their answer, they weren't "bamboozled" into selling the product to companies with ill intent. So either Intel was bullied into selling the wrong product (meaning they are weak and/or don't care about their brand), or they didn't care about the consequences for consumers.
Either option is ugly for Intel, and even still they handled things poorly:
1) They put their name on a GPU that was developed by Imagination Technologies, using drivers written by Tungsten Graphics. I have serious doubts the PR department was contacted before making this decision. This is my biggest beef with the company, because they've built up my trust as a company that supports Linux with their product line.
2) Even with the above change in dealing with the Linux (and computer users in general) community, Intel fails to accommodate us in other ways. NVIDIA has closed drivers, and yet they manage to honor Linux users with usable video drivers. Do I wish NVIDIA had open drivers? You bet. But at least they provide usability.
3) Rather than provide ABSURDLY limited Linux drivers, Intel should have just not supported Linux at all. I feel most sorry for those folks that bought the Dell Mini 12 with Ubuntu pre-installed. Certainly if Ubuntu was pre-installed the hardware would be Linux compatible. Um, nope. Yes, perhaps Dell should have read their contract with Intel better, but come on, Intel sold their stuff with no upgrade path? I'm sorry, but that's just dumb.
So in the end is Intel the only company to blame? I suppose not. Dell, Acer, Sony -- you guys should have known better. In fact, with this black eye, perhaps you have learned and won't trust Intel anymore. If only there were other companies making CPUs... (PS: Hey guys, I can provide you with links if you need them)
And even if you buy into the idea that Intel is blameless in this GMA500 debacle, they're certainly the only folks that can fix it. So I reiterate:
Please do something. I don’t want Windows on my Acer, and I’m sure there are a lot of folks with the Dell Mini 12 that would rather not keep their old version of Ubuntu in order to use their netbook. We’re still friends, let’s make up, OK? Make it right, and we’ll chalk this up to a bad oversight.
Linux User, Linux Journal Associate Editor, and Intel fan with a bone to pick.
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
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Tech Tip: Really Simple HTTP Server with Python
- Rogue Wave Software's Zend Server
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