Nobody can stay on top of everything. That's why it came as a bit of a surprise to me when I got a note from a colleague that consisted entirely of this: "Lindows: scoundrels or fools?" I didn't know what he was talking about. Then somebody else pointed me to an AP report that Microsoft had sued Lindows for having a name that rhymed too closely with Windows. This person annotated the story by giving it the subject, "suicidal or dumb?"
Now I was up to four choice characterizations: scoundrels, fools, suicidal and dumb. And it wasn't even clear if the labels were meant to apply to Lindows, Windows, Microsoft or all four -- since Lindows is the name of both the company and its only product, an OS that runs both Linux and Windows.
(By the way, if we didn't use the target tag for that Windows link in the last paragraph, the page would trap you there by disabling your back button. How metaphorical is that?)
Lindows is the creation of Michael Robertson, the cofounder and former CEO of MP3.com, which is now part of Vivendi Universal. About the lawsuit, Robertson told the Wall Street Journal, "There's not a single person, perhaps outside of the 600 attorneys that work for Microsoft, who can say with a straight face that people will confuse" Lindows with Windows. The Journal also observes that, while Microsoft employs about 600 people in its law and corporate affairs unit, not all of them are lawyers. This probably does not reassure Mr. Robertson, although there could hardly be more sure-catch lawsuit-bait than his company's name and mission.
About the latter he says this:
Many of you have taken the time to write me about my new venture Lindows.com; and I've tried my best to personally respond. The most common question asked is, "Why are you doing Lindows.com ?" The answer is straightforward -- the world needs it, the technology industry needs it, computer owners need it. What is 'it' you ask? Choice. Putting another choice on the shelf for consumers is the ultimate tonic for high prices, restrictive licenses and intrusive security measures. The power to choose means consumers will be in the drivers seat and not beholden to the policies of one company.
Sounds fine, except for that "consumer" label, which we rarely hear in Linux circles (where the default would be "users" or "customers"). Still, these are honorable motivations, and perhaps commercially viable ones as well.
Robertson goes on to say that LindowsOS is a Linux-based operating system with a "Windows Compatibility Module". I assume this means he's talking about something that involves WINE, but he doesn't say. Nor does anything else on the site. The closest thing to a technical section is an FAQ that tells us LindowsOS will cost $99 and run on Pentium-class hardware with at least 64MB RAM and 1GB disk space.
Right now LindowsOS is vaporware. But the company does have a highly entrepreneurial CEO. I think they have some potential in the low-end hardware market if they can make everything work. Let's face it: Linux-based thin clients haven't set the world on fire. Not yet, anyway. Maybe running Windows apps natively would be the right gas for that job. Hardware has gotten cheaper, but while Moore's law continues to drive up performance, there's a price floor that gets a lot lower when you subtract the rising cost of Windows, especially considering XP's one-OS-per-machine authentication scheme.
The question for me is, can they do it alone? Clearly Lindows is a closed-source company building a product with open source code and tools. Do they really need to close the source? Do they actually plan to? I don't see them listed as an exhibitor at LinuxWorld, which would make sense if they wanted to join the community. Seems to me they could use a few more eyes to make their bugs shallower. It's doing the job for Apple with Darwin, and attracting serious geeks in the process.
So I don't know. In the absence of more information, the choice still defaults to the original four. What do the rest of ya'll think?
Doc Searls is Senior Editor of Linux Journal
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Dynamic DNS—an Object Lesson in Problem Solving
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Please correct the URL for Salt Stack's web site
2 hours 25 min ago
- Android is Linux -- why no better inter-operation
4 hours 40 min ago
- Connecting Android device to desktop Linux via USB
5 hours 8 min ago
- Find new cell phone and tablet pc
6 hours 7 min ago
7 hours 35 min ago
- Automatically updating Guest Additions
8 hours 44 min ago
- I like your topic on android
9 hours 30 min ago
- This is the easiest tutorial
16 hours 6 min ago
- Ahh, the Koolaid.
21 hours 45 min ago
- git-annex assistant
1 day 3 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?