Manufacturer: Lindows.com, Inc.
Price: $59.95 US (download version, $49.95 US)
Easy install with hardware detection.
Slick package management.
Family license might be a good deal.
Poor security—defaults to always running as root.
Rough edges could confuse new users.
Many packages confusingly renamed.
Lindows is a Linux distribution intended to be as easy to use as possible, even for complete beginners. The Lindows promotional literature promised a ten-minute install, and indeed, the process took about ten minutes.
Lindows 4.0 comes with two CDs. One is the installation CD, which detects all your hardware and installs Lindows. The other is a demo CD, which detects all your hardware and then runs Lindows in RAM, loading any applications directly from the CD. You can use the demo CD to try out Lindows 4.0 on a computer without overwriting your data. I booted up the demo CD, and it worked as advertised. It let me experiment with Lindows and did not write to my hard disk.
Next, I installed Lindows on a spare computer. When you begin the installation you are offered two choices: automatic disk partitioning (labeled “take over the whole hard disk”) or manual partitioning for advanced users. I let the Lindows installer take over the whole hard disk. It created a small boot partition and a 256MB swap partition; it then filled the rest of the disk with a single large ReiserFS partition.
The installer asked few questions, none of which concerned what kind of hardware the computer had; the installer detected hardware without prompting. At the end of the install, the installer prompted me to enter an optional system password. This password is, in fact, the root password. By default, Lindows sets up the user to run as root all the time and only weakly encourages the user even to set a password for root. This design certainly is a convenient way to set up a system, but it gives up much of the traditional security inherent in Linux.
Lindows is based mostly on KDE. The desktop is a KDE desktop, heavily customized with the Lindows brand. The custom theme's icons run to green and blue colors that match the Lindows logo.
Lindows 4.0 defaults to Mozilla for both Web surfing and e-mail. Mozilla is rebranded as “Lindows Internet Suite”, and unless you run mozilla --version at a shell prompt, it is difficult to figure out that it is version 1.3.
Konqueror, rebranded as File Manager and Web Browser, is the default file manager for Lindows. Desktop icons for My Computer, My Documents and Network Browser all open Konqueror to the appropriate location.
When I tried out a command prompt, I discovered that Lindows was missing some important tools, such as the man command. Fortunately, Lindows is based on Debian GNU/Linux and contains a working core Debian system. By running apt-get I was able to install man, vim and other must-haves for the more advanced user.
The most impressive part of Lindows is the Click-N-Run system. With Click-N-Run you can browse through a virtual warehouse divided into categories, with aisles (departments) containing software packages. For example, in the Multimedia & Design category you can find an aisle named Image Editing, which contains various image editors including The GIMP. If you click on the Click-N-Run icon next to The GIMP, it is added to your Click-N-Run queue and automatically installed.
Because Click-N-Run starts up as soon as you log in, it can download software continuously in the background while you work. As long as you are connected to the Internet, Click-N-Run downloads packages until your queue is empty again. You can open the Click-N-Run client to check on the status of your queue and to see what's already installed, see what's pending, cancel pending downloads and so on.
One nice touch, the Programs menu in the main program launcher is organized exactly the same as the Click-N-Run Warehouse. Thus, after you have installed The GIMP, you can find it by clicking on Start Applications, Programs, Multimedia & Design, The GIMP. The icons on the categories are the same icons used in the Click-N-Run Warehouse as well, so the system is visually well organized, too.
In order to use Click-N-Run, you need to sign up with Lindows for a Click-N-Run account. This costs from $50 to $150 US per year, depending on what level of account you choose. Much of the Click-N-Run software is free software, such as The GIMP, but some proprietary software also is offered. If you use Click-N-Run to download a proprietary package, you are billed automatically.
Among the available proprietary software packages are VirusSafe, a virus scanner based on Vexira Antivirus, and SurfSafe, a Web site blocker based on the Cerberian Web Filter. With SurfSafe in place, trying to access a site like playboy.com brings up the “LindowsFamily — SurfSafe Warning” page.
Click-N-Run isn't perfect. When I installed MPlayer, it didn't work, but returned with no error message—it simply shut down. By running MPlayer from a command prompt, I was able to see an error message explaining that the .mplayer directory was not set up correctly. But Click-N-Run worked well for the other packages I tried.
I was somewhat annoyed at the relentless rebranding of packages that exists in Lindows 4. KWrite, the KDE word processor, is available in Click-N-Run, but it's called Write Pro. GTKPool is called Billiards; Gnumeric is rebranded as Numeric. Some other packages retain their names—but does a typical Lindows user know what TK Gocr is? If Lindows needs to come up with friendly names, I would hope they include the original name in the new one, as they do with XGalaga Galactic Invaders. Or, at least mention the original name somewhere on the Click-N-Run information page.
In the future, it should be possible to use Click-N-Run to upgrade from a previous version of Lindows to a newer one. However, Click-N-Run currently cannot upgrade from Lindows 3.0 to Lindows 4.0; you need to use the Lindows 4.0 CD.
|Designing Electronics with Linux||May 22, 2013|
|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|
- Designing Electronics with Linux
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Validate an E-Mail Address with PHP, the Right Way
- Tech Tip: Really Simple HTTP Server with Python
- Why Python?
- Build a Skype Server for Your Home Phone System
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Reply to comment | Linux Journal
57 min 5 sec ago
- Reply to comment | Linux Journal
1 hour 47 min ago
- Not free anymore
5 hours 49 min ago
9 hours 36 min ago
- Reply to comment | Linux Journal
9 hours 44 min ago
- Understanding the Linux Kernel
11 hours 59 min ago
14 hours 28 min ago
- Kernel Problem
1 day 31 min ago
- BASH script to log IPs on public web server
1 day 4 hours ago
1 day 8 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?