I was cleaning out some old e-mails this morning when I came across a link to an article I had saved last November. Katherine Noyes of LinuxInsider reported the release of 64-bit Adobe Flash for Linux. In her article, she cites a post by blogger Julian Saraceni titled “Stop pirating Adobe Software, Use Free Software Instead”. Both are quick reads and I recommend them.
Commercial software can be expensive, but in my experience, the old adage “you get what you pay for” holds true more often than not. As you might expect me to say, the price of software is driven not only by what people want to pay, but also by what authors are willing to charge. The cost of developing, testing and maintaining software must be recouped and an adequate profit margin added on top of that to keep software companies interested. That’s an economic reality.
Many people feel that software prices in general are unreasonably high. I’ve found that the justification for this belief is usually relative to the specific person’s financial situation at the time, but in many cases I agree that software is overpriced with respect to what you get for your money. Really good software is worth every penny. The perception that software prices are not fair is one of the main reasons people commit piracy.
Piracy does have serious, far-reaching consequences. The most direct economic effect is felt by the authors and sellers, but economic imbalance has a way of rippling through an entire economy, through the product and labor markets in many sectors – the problem is not isolated. As piracy becomes more acceptable, a skewed sense of property rights develops. Society’s standards change and the peoples’ sense of right and wrong dulls. Theft, of which piracy is just one type, is more easily justified and thus, committed more frequently and even casually. Respect for the rights of others, and therefore respect for others themselves, is abandoned and the social contract decays.
OK, I’ll get off my soapbox now. Where’s the FUD? “Everyone” knows that the Linux community was started by a “bunch of hackers” and the negative connotation that accompanies that statement is well-understood. “You Linux people want everything for free!” This perception unjustly deposits the Linux community in the same class as pirates. I occasionally come across the accusation that Linux egregiously promotes piracy, though this is most often made in the context of copyright violations in the entertainment industry.
The truth is, (intellectually) Free Software is available to those who disagree with the concept and/or laws of intellectual property. Usually, Free Software is also (gratis) free or low-cost software, because intellectual protection is often what permits software price gouging. The authors are usually the first users of a Free software package, so overall quality is generally higher than one might expect. As expressed in the articles above, the availability of Free Software should reduce or eliminate the perceived “need” for piracy. Free Software is not limited to the Linux platform, but the Linux community supports and fosters this mentality explicitly.
Perhaps we can solve the problem of piracy at the root. (pun intended)
Since the announcement that Best Buy started carrying the ASUS Eee PC 900A in their stores at a new US$299 price point (down to US$280 just yesterday), I’ve been keeping my eye on the market’s reaction. Whilst researching, I ran across several interesting posts that tie into the “Linux will void my warranty” FUD pattern. Apparently, there have been two concerns over the warranty for this line of netbooks.
The first has to do with a sticker that appeared on the bottom of some units indicating that opening the unit will void the warranty. This is unthinkable – even a simple RAM upgrade, which many folks do immediately upon purchasing an Eee PC, requires opening the access panel on the bottom. Indeed, ASUS agrees and has publically clarified that this is not the case.
The second concern, and one that I find more interesting with respect to the FUD pattern, is that ASUS will only support the default Xandros flavor of Linux. Reportedly, “Asus is not responsible for software misconfiguration, such as troubleshooting an alternative operating system.” It does not state that running another Linux flavor or MS Windows will void the warranty (in fact, the posting makes that explicitly clear), but it does show that ASUS is limited in the service they can provide if the OS is replaced. This is not much different than what HP’s warranty conditions state.
Linux FUD Pattern #8: Linux will void your warranty
Will the use of Linux void the manufacturer’s warranty of your computer hardware? This is one fear that prevents some people from making the leap to Linux, which is why it is on my Top 10 List of Linux FUD Patterns. The short answer is, it depends; however, there are steps that you can take to increase your probability of receiving service under a warranty.
What Is A Warranty?
A warranty is a seller’s obligation to provide a remedy when a product fails to meet the conditions of the warranty. The conditions and the remedies are specific to the warranty for a product, though some warranties are legally implied and need not be explicitly expressed. The Federal Trade Commisison provides a very informative page describing warranties.
Conditions under which a buyer may exercise the right to receive a remedy usually concern attributes of product quality. Express warranties are an incentive to the buyer, because it shows that the seller is willing to stand behind its products and protect the consumer from unintended defects that arise during manufacturing or during normal use. The definition of normal (or “intended”) use may be specified in the conditions.
In the United States, Article 2 of the Uniform Commercial Code governs warranties, both express and implied. Sellers are legally limited in the extent to which they can disclaim warranties. Specific statutes are established at the state level. Moreover, the Magnuson-Moss Act of 1975 was enacted to make warranties more readily understood, but its application is limited to consumer (read: household) products.
Why Not Honor Warranty Claims?
Why would a company not want to honor a claim made against its product warranty? In a word: cost.
Warranties are considered to be contingent liabilities for financial accounting purposes. At the time of sale, a reasonable estimate of warranty costs can often be made. This also means that until the costs either are realized (e.g. warranty work is performed) or expire (e.g. at the end of the warranty period), the obligation to replace or repair the product in question impacts the financial health of the seller or manufacturer. Depending on the product, such obligations can be significant. Financially, expiration is much better than realization because it does not impact cash.
Moreover, the cost of troubleshooting and repairing a system with a nonstandard OS installed is higher than that for a standard configuration because time must be spent either learning to work within the unfamiliar operating environment or time is spent working around that environment. It’s also much easier to determine when a problem is not a result of manufacturing or normal use when the technician is working within a known environment as it has been (pre)installed by the seller. If you replaced the software used by your automobile’s internal computer with a variety of your own, do you really think a dealership or even an independent mechanic is prepared (much less willing) to assist?
What’s worse, if a component of a product that provides some sort of control over the use of the product for the purpose of maintaining or extending its useful life, then the replacement or modification of that component may cause hard to the product as a whole. This is obviously not a manufacturing defect and is unlikely to be considered “normal use”. The extent to which an OS fits this description depends on what functions the OS provides (e.g. teperature control).
Read Your Warranty!
Ultimately, the answer to the question lies in the language of the warranty itself. A statement of warranty is a legal document and the one shipped with your new PC was probably written with or by a lawyer. The specific conditions and remedies are contained therein. READ YOUR WARRANTY! This will be the primary source of coverage information should you decide to take a dishonored claim to the courts. If it is that important to you, read the warranty before you buy the computer and only buy a computer with a favorable warranty.
Rest assured, the company will probably steer clear of violations of implied warranty, which means that they will probably not refuse to replace items that pose grave safety hazards, such as exploding laptop batteries. Dealing with your non-standard OS is much less costly than a court settlement with your home insurance company or your estate. A motherboard or power supply that stops working altogether is not a grave safety issue and claims regarding these issues are subject to more scrutiny.
HP Case Study
An exegesis of each and every warranty provided by every PC manufacturer over time is far beyond what I can do here. But, since a Web search for ‘Linux’ and ‘warranty’ readily retrieves stories about Hewlett-Packard, and since my family has two HP laptops in the household currently, I decided to do a little research on their warranty specifically. Here’s what I found, followed by an account of my own experience with HP support.
The HP warranty is published online, so rather than quote what is on my warranty card, I thought it might be more useful for the reader to have access to the warranty disclosed publically. In the first paragraph of the “Limited Warranty” section, the application of the warranty conditions is expressly limited to hardware products and specifically excludes software and non-branded peripherals. The section continues to explain the HP guarantee, the customer’s entitlement to receive hardware warranty service, and the conditions for repair or replacement.
The “Software Limited Warranty” section near the bottom of the warranty page explains that HP’s obligations are limited to defects in the removable media (i.e. floppies, CDs, DVDs, etc.) shipped with the product, and then, for only a period of 90 days. Of course, the chance that an average PC customer is actually going to use the recovery or installation CDs for a preloaded PC within 90 days, especially for the express purpose of testing the media for defects, is pretty remote – good thing the expectations weren’t set too high for software.
That section also explicitly disclaims support for “freeware operating systems and applications.” Yes, Linux is Open Source and not freeware, but then, the actual verbiage of the paragraph refers to “software provided under public license by third parties” and that would include an aftermarket installation of any GPL software.
So far, so good. Hardware is supported and software isn’t. Uh oh…
There is a possible out for HP in the “Customer Responsibilities” section. For “best possible support”, the customer must be able to “run HP diagnostics and utilities” and even allow HP to monitor using “system and network diagnosis and maintenance tools”. No doubt, these are compiled for Windows only. “I’m sorry, we cannot fix a problem that we cannot diagnose. Good bye.”
This doesn’t mean that HP will not support you, but it does provide them with a logical and reasonable excuse not to do so. Indeed, HP reportedly clarified in early 2007 that the installation of Linux does not affect the warranty of the hardware so long as the software is not the cause of the problem being fixed.
Here is a case in point. In recent months, HP issued a recall of specific models of the Pavilion laptop due to a BIOS problem. As I understand it, the problem had something to do with the computer’s ability to regulate temperature, so units would overheat. Battery problems and other component failures were extreme symptoms. My wife’s laptop was one of the models listed, so I called tech support to schedule a repair. During the course of the conversation, I told the representative that I would remove the hard drive prior to shipment, primarily because it contained sensitive data (which was true). I also mentioned that Linux was installed and that the hard drive would be of little value in the repair process. The rep said that removal of the hard drive was acceptable. The unit was fixed and returned without incident.
How To Protect Your Warranty
Based on my experience and research, here are a few things that you can do to help ensure warranty service:
Troubleshoot the problem. If you are tech-savvy enough to run Linux, you probably know a thing or two about computers. Troubleshooting problems is a science, not an art, and the more you isolate the problem to a specific component, the more leverage you have with the warranty organization.
Buy a second hard drive. The only evidence of a Linux install is on the hard disk (unless you’ve replaced the Windows case badge with a Linux one, of course). When you buy a new PC, set up the preinstalled system, register it, remove the hard drive and store it in a safe place should you need to run vendor-supplied diagnostics. Buy and install a second hard drive for your Linux install and go to town!
Retain possession of your hard drive. Do what I did and tell them that you will be sending the unit in for repair sans hard drive. Data security is a big deal, even more so if the data in question is your employer’s data! Besides, the worthy repair facilities have their own diagnosis disks to use in lieu of a customer’s drive. You need not mention Linux at all. Of course, you cannot expect them the repair or replace a hard drive if you do not furnish the broken one.
Play it safe. Do not use software or perform other system tweeks that have the potential to harm hardware if you want the warranty honored. It is very unlikely that a standard Linux distro will cause such harm, but Linux does provide much more software access to hardware components than do other consumer operating systems. You may be surprised how easy it can be for the experts to determine how a component burnt out and the probable reasons as to why.
|<< Go To Part 7||Part 9 Coming Soon >>|
This article contains information on warranties, but does not contain legal advice. Opinions expressed herein belong solely to the author. If you have a warranty issue that may necessitate legal action, please contact a lawyer.
I’m soooooo glad that the PC Weenies have taken the time to explain the Microsoft commercial! The Shoe Circus is a Mac Store slam and Microsoft’s future is a fried snack.
P.S. You probably know by now that I believe in supporting artists, and revelations like this don’t come along everyday, so please commemorate this occasion by ordering a copy of this cartoon on card stock today!
The new Microsoft commercial featuring Jerry Seinfeld and Bill Gates aired for the first time late last week. I caught it yesterday morning, but was on a treadmill at the gym and couldn’t hear what they were saying, so I had to catch up on YouTube.
I usually try to link some good references for you, but there are just too many articles and ‘blog posts to cite on this one! Most claim that the ad was too expensive for so little content. I agree and would like to add that it was too long…a minute and a half! Throw in some commercial breaks and some yada-yada-yada and you have a full-legnth Seinfeld episode!
I actually got more out of the ad without sound. It appeared that Jerry was going the extra mile to provide good, personal customer service to Bill in the shoe store, explaining in great detail how a particular brand of shoe, the “Conquistador”, is quality-tested for ruggedness. I could see the gears in Bill’s head turning as he absorbed Jerry’s message and pondered how he could reap the benefits of quality-testing at Microsoft. Once I heard the commercial, however, I felt the urge to buy a pair of Conquistidor shoes and was suddenly hungry for a churro. Upgrading my OS or office productivity software was the last thing on my mind.
If subsequent commercials don’t send a clearer message, I may have to start a FUD ‘blog to warn consumers about the fear, uncertainty and doubt campaign Microsoft is waging against itself. You know, just to be fair, right?
Bill Gates publicly stepped down from his position at Microsoft on June 27, 2008. He will not be missed, at least not by me, nor by many Linux users around the globe. There is a lot of speculation in the blogosphere as to what this means for Linux over the next few years. Some see it as the inevitable demise of Windows, the beginning of the end, but I’m not yet convinced.
When asked what will become of Linux when Linus Torvalds is no longer involved, advocates are quick to respond that Linux is a product of the community and relies not on one man, but on an underlying framework of goals, practices and beliefs. So, too, it is with Microsoft. Gates’ departure may be portrayed as the loss of a beloved general or king, but his absence may very well make room for the innovative minds needed to lift the company to new heights.
Let’s not count our penguins before they are hatched, my friends! There is much work yet to do!
In January, I wrote at length about the perception that Linux is not ‘officially’ supported. Yesterday, Linux-Watch released some figures that demonstrate how much of work toward the development of the Linux kernel has been contributed by paid professionals hired by large, profit-seeking corporations. Yes, I said paid professionals.
Two great quotes from Linux Foundation Marketing Director, Amanda McPherson, can be found in the last few paragraphs, both in relation to the unthinkable notion that profit-seeking companies would expend resources (money, time, people) improving something that they do not exclusively own and cannot sell. She notes that a savings from shared R&D costs do ultimately impact the bottom line (i.e. profit increases due to a decrease in expense, not an increase in revenue). I suspect that she wouldn’t be mentioning this if the cost savings weren’t (or weren’t expected to be) material.
McPherson also notes that “it’s difficult for most people to get their minds around competitive mass collaboration.” Indeed, this is what the freedom afforded by Linux is all about. People (and companies) contribute not for humanitarian reasons, but because they expect a benefit. Work together to create the best platform, openly usable by everyone, and if it still doesn’t meet your needs perfectly, you are free to change it accordingly. Everyone wins. No compromises.
Here is an interesting post from The Angry Admin ‘blog. The basic point being made is that Microsoft has succeeded in corrupting the ISO standard-setting process, attempting thereby to shake the faith in it and the standards that arise from it. Perhaps the title of the post should have made reference to the death of ISO, not ODF. Near the end, the company’s proficiency in FUD is highlighted; but, if true, it also reveals a slight difference from Microsoft’s typical modus in that a stalemate was considered acceptable. When it’s not winning the game, the company usually either bullies the other kids until it is declared the winner or picks up its toys and goes home; in this case, it opted to raze the playground. Could this be a sign of a weaker Microsoft? Maybe, maybe not. Time will tell.