Can a Red Hat Guru Survive on a Lindows Laptop?
I have been looking for a laptop for a long time. My old IBM Thinkpad, being a 90MHz Pentium with a maximum RAM capacity of 40MB, is no longer useful for the things I need.
I had decided I wanted a modest machine that I could use on the road; I did not want this laptop to be a desktop replacement. I merely wanted to use it for Web surfing, e-mail and the occasional presentation while on the road. My primary workstation would continue to be the tower I have in my home office.
I finally found a Dell Inspiron 5100 with a fast processor and 512MB of RAM at a price I could afford. I got a 14" screen and the default 30GB hard drive to save money. It also has a built-in modem and Ethernet adapter.
My new laptop came with Windows, which I will not use. To give you some sense of where I am coming from, I have used DOS, OS/2, TopView (remember that?) and Linux but never Windows as the primary operating system of any of my computers. I have been using Red Hat since version 5, and I even worked for Red Hat for a while, teaching RHCE classes, so I am quite familiar with the Red Hat and Fedora distributions. Now, however, I just wanted to get this laptop up and running with as little hassle as possible. It sometimes can be a struggle to install and configure Red Hat correctly on laptops. A lot of help is available, but it can take a great deal of time to find, install and configure the correct drivers.
My objective with this laptop is to have a relatively lightweight means of accessing my other computers, so I can manage them while on the road. I need LAN and dial-up communications, and I would like to have wireless as well, although that is not yet a necessity. I want the ACPI power functions to work, and Lindows recently (as of this writing) released their Laptop Edition. Because Lindows advertises it as being configured to work with many different laptops, I thought I would give it a try.
I decided to install Fedora Core 1 as a control to get a basis for comparison. It took about 10 minutes to go through the configuration portion of the Fedora installation, and about an hour to complete the installation.
Fedora had trouble probing the standard Dell laptop LCD screen, but it did find and configure properly the video adapter, an ATI Radeon Mobility 7500, and the Broadcom NIC. It did not recognize the modem, and power management did not work. The 5100 uses ACPI rather than APM, which is how the Fedora kernel is compiled. I could have recompiled the kernel, but doing so would not allow me to meet my objective.
I purchased the digital download of Lindows Laptop Edition from the Lindows Web site. After $49.95 was charged to my credit card, I attempted to downloaded the ISO image. The download took several attempts, because I would get only half of the image before the download would hang. After a couple of frustrating hours, I finally was able to burn the image onto a CD-ROM.
I popped the newly minted Lindows CD into my laptop's CD-ROM drive and rebooted the system. I was not fast enough on the F2 key, and Windows XP insisted on booting quickly and going through its installation configuration. I had to unplug the charger and pull the battery in order to reboot, because the configuration had blocked Ctrl-Alt-Del. I managed to get into the BIOS setup after about three tries and set the boot sequence to CD-ROM. I then finally made it into the actual installation.
The installation gives you two installation options: you can choose to install in an existing partition or you can take over the entire disk. I chose to take over the entire disk, because I really wanted to get rid of that other OS. After a few minutes, the installation crashed and returned the message that it had failed to create the new partitions.
A reboot showed that all of the existing partitions had been deleted, and the second attempt worked fine. All I did to complete the installation was enter the computer (host) name and an administrative password.
It took only five minutes or so to do the complete installation. When it finished I thought there had to be some mistake, but it really was finished.
Booting into the installed Lindows Laptop Edition for the first time is very clean, but it might be somewhat frustrating for expert Linux users. None of the boot time messages we are used to fly by, but considering the target audience, this is probably a good thing. I know too many people who would panic over all those messages.
The loud music emanating from the built-in speakers told me in no uncertain terms that Lindows had found the sound chip.
After I agreed to the EULA, the tutorial started automatically. I glanced at that, but closed it and got on to the important stuff. The EULA is what Lindows calls a Family License, and each user must agree to its terms the first time he or she logs in. New users also are treated to the tutorial, which is well done and looks to be thorough and complete for a typical user.
The ACPI power functions worked correctly, and I actually could see the state of my battery on the battery icon. Lindows also detected both of the CUPS printer shares on my print server. So far so good.
Because Lindows boots to root, I used the User Manager to add an account for myself as a regular user. The command-line useradd is not configured to provide the same defaults in Lindows as it does in Red Hat. If you choose to use useradd for adding new user accounts, you will have significantly more manual work to do, including specifying the home directory name and default group. You also have to create the default group.
|The True Internet of Things||Sep 02, 2015|
|September 2015 Issue of Linux Journal: HOW-TOs||Sep 01, 2015|
|September 2015 Video Preview||Sep 01, 2015|
|Using tshark to Watch and Inspect Network Traffic||Aug 31, 2015|
|Where's That Pesky Hidden Word?||Aug 28, 2015|
|A Project to Guarantee Better Security for Open-Source Projects||Aug 27, 2015|
- The True Internet of Things
- Using tshark to Watch and Inspect Network Traffic
- September 2015 Issue of Linux Journal: HOW-TOs
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- Where's That Pesky Hidden Word?
- Firefox Security Exploit Targets Linux Users and Web Developers
- Concerning Containers' Connections: on Docker Networking
- A Project to Guarantee Better Security for Open-Source Projects
- Build a “Virtual SuperComputer” with Process Virtualization
- My Network Go-Bag