Vendors and Drivers and Hardware, Oh My...
In my video last week, I really hammered on Hewlett Packard. It's important to realize, however, that they are merely the vendor that happened to irk me at just the right time. My video could easily have been pointed at any number of tier one computer hardware vendors, and it would have been just as heartfelt. In fact, I'm rather fond of HP, and so addressed my video to them in the hopes they would listen.
I have a phone meeting with them
Monday [Sometime soon, meeting rescheduled], so I suppose we'll see what happens.
I do want to clarify a bit though, because in the emotional outcry, some of the keys to my frustration may have been unclear.
- Drivers for Linux. HP tends to be a "Linux Friendly" vendor. I realize that. Heck, when I buy HP servers, they have the option to install Linux using their custom installation CDs. I really appreciate that, and therein began my fondness for HP.
- "Drivers" Doesn't Mean Open. I wouldn't have wasted my breath 5 years ago with a message to vendors. Admittedly, times are slowly changing. I want it to be clear that while I do appreciate their efforts: Half supported chipsets, closed source kernel modules, and undocumented hardware really isn't what we were asking for. (Or if it was, we weren't specific enough) Wireless adapters are a prime example of this. Atheros cards are a pain in the butt, and while we can get them to work -- it's only because we are willing to work really hard to do so. I'm far from alone in this frustration.
- Who's In Charge? I'm embarrassed for vendors when they act like puppets on strings for Microsoft. Blurbs like "HP Recommends Windows Vista Business" on hardware that is also available with Linux is exactly the same thing as saying, "HP Recommends You Don't Use Linux." And why wouldn't the average buyer listen to them? I mean, after all, they're the hardware vendor. They recommended Vista, so it must be the better choice. I'm pretty sure Microsoft doesn't need the help getting market share. HP is just perpetuating the myth that Windows is better. That is what bothers me about the sticker.
- If You Don't Like It, Don't Flaunt It.. The HP-2133 is an obvious answer to the ASUS EeePC. Asus garnered its fame due to size, cost, and Linux. HP used "Linux" in their advertising to make it more clearly their "Eee Killer" -- but their followup makes it pretty clear that Linux was just a marketing scheme.
ASUS versus HP, a fictional set of press releases I made up to make my point:
ASUS: We have a small, affordable computer running Linux. We'll give you Windows drivers if you like, but realize you'll have to spend money buying Windows. We chose Linux. (Yes, they later offered pre-installed Windows, I realize that, but it was very clear Linux was NOT the second class citizen)
HP: Hey wait! WE have a tiny Linux laptop too! No, really, we do! Ours is bigger and better, and only slightly more expensive! (But really, we don't recommend you buy the Linux version, we recommend you buy the computer with Windows Vista Business. It's more expensive, and you will have to purchase even more hardware to fully benefit from Vista, but it's what we recommend. Really. Seriously. See, we put it on the sticker.)
I'm not saying that ASUS is the perfect vendor either. If you've tried to get wireless networking to work on the EeePC, you'll quickly find that the Atheros chipset is frustrating. (See my point #2 from earlier) I sure do like the way they introduced the EeePC though. And so did LOTS of other people, both the Linux geek and the Average Joe alike.
Will my video rant make a difference? In the short term, probably not. If we don't continue to make our will known, however, things will never change. All too often we just accept hardware as it is, because we're smart enough to get things working regardless of the help we get (or don't get) from vendors. Personally, I'd rather see our efforts put elsewhere, and I thought vendors should know. If you agree, be sure to let your sales rep know. If we don't tell them, they might never have a clue.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Returning Values from Bash Functions
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Google's SwiftShader 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