Welcome!

Linux Containers Authors: Elizabeth White, Zakia Bouachraoui, Liz McMillan, Yeshim Deniz, Pat Romanski

Related Topics: Linux Containers

Linux Containers: Article

Migrating to Linux not easy for Windows users

The marketing blather promises easy upgrades, but that's not what one newbie found

(LinuxWorld) — Windows 95 works well enough for my needs, but I'm eight years behind the technology curve. While I realize there are still many who rely on Apple IIs and Tandy 100s for their daily computing chores, it's time for me to start planning a migration route. I was mulling the possibilities when the OfficeSuperGeek (tOSG) talked me into a CPU upgrade, gave me a suitable motherboard from his bonepile, dumped some Linux distributions on my desk and said, "Here... try these." What follows is an 18-month tour of recent and now not-so-recent Linux distributions.

Before we proceed, let me set your expectations about this overview. It isn't scientific. It's based on my impressions as a technical writer, Linux neophyte and curmudgeon. It's an appropriate and fair look from my humble newbie perspective. If you are a hairy-chested Linux administrator or programmer, you will undoubtedly find yourself screaming as you read the following. Save your breath. Here's what I want:

SUBHEAD2: The migration destination

My non-negotiable requirements for a new operating system center on simplicity for me. Spare me your "how much more enlightened, knowledgeable and confident I will be if I know the intimate details of my computer if the installation is treacherous!" speech; I want an operating system that works like a Honda Accord and not a kit-car project.

  1. It must have a GUI interface for installing and configuring the system. I'm a lousy typist, and text mode is not an efficient way for me to interface with an operating system.
  2. Existing hardware must remain usable. At a minimum, the printer, modem, and CD player/writer must work, and the new operating system must make them work without my having to tweak configuration files. If it can't get that far, it's not ready to inflict on the general public as a migration route, and I certainly will not recommend it to my friends.
  3. Existing software must remain usable unless the new operating system has equivalent features to the ones I use, there is no loss of data and data-transfer is easy.

    Note: Requirements 2 and 3 eliminate WindowsXP as an upgrade route. I would need to buy a new computer, probably new peripherals, and replace some eXPensive software to get the dubious benefits of product-activation codes and embedded functions I don't want and can't delete.

  4. A bit of incompatibility with legacy Microsoft Office documents is OK, but using an old Microsoft Office file with Linux should be no more of a pain in the neck than using an old Office file with a new version of Office.
  5. I must have the ability to edit documents created by clients with Windows systems and return them to the client in their preferred format.

    Requirements 4 and 5 can be handled by OpenOffice.org's 1.01 release. It doesn't have perfect compatibility with MS Office files, but it's as compatible as any version of MS Office is with any other version.

    It looks like the solution is a dual-boot system with Win95 and Linux.

  6. Because a dual-boot system is the best solution for me, the Linux distribution must make it easy to create a dual-boot system. It has to recognize and preserve the existing operating system and its data, give me access to the data on the Windows drives and be reasonably unlikely to wipe out my system.

Expectations & foreshadowing

It was supposed to "just work." (Note the foreshadowing here, folks. The supposed to is a big hint.)

I assumed that I would partition drives to make room for Linux, set the BIOS to boot from a CD-ROM drive, reboot with an installation CD in the drive, make some on-screen selections, let the distribution know what hardware to use, twiddle my thumbs for a while as it loaded software and then have a working system. I expected the installation routine to configure whatever needed configuring after it detected the hardware or I told it what I had. That's what tOSG expected, too.

My installation approach

I have installed various Linux distributions on four variations of my PC over several months. If a system is not mentioned for a distribution, it's probably because the hardware was no longer available at that time. I did not test all my requirements on all the systems. If a distribution flunked a major requirement, it was pointless to continue.

Bare essentials
GUI interface for installation/configuration
Existing printer, modem and CD-R drive must remain usable
Existing software must remain usable or have a Linux-friendly equal
Compatibility with Microsoft Office documents and files
Can create a dual-boot system

Before each installation, I deleted the Linux partitions from the drives and restored them to formatted FAT32. I did this so that every test could start with the same conditions, as if a user were doing his or her first installation.

This is more of an experiment to see how ready Linux is for the average Windows-user than how it stacks up for my own migration to Linux. As a technical writer, I've watched users install software. They have amazing faith in the programmers who write installation modules. A typical user follows on-screen instructions, clicks the most obvious choices, accepts the defaults and seldom resorts to reading manuals. If Linux is to become an upgrade path for ordinary Windows users, at least one distribution has to be installable the way the ordinary non-geek computer user will install it.

To give the distributions a real-world test, I used only the help sources provided with the distributions. I can hear some of you now:

  • "The newsgroups are where you should go for help!"
  • "Website 'A' has the documentation you need!"
  • "You have to read the man pages!"
  • "Use 'apropos'!"
  • "It takes an expert to install and configure an operating system!"

Well, you shrieking geeks, I don't have a shelf full of Linux reference books, and I don't plan to buy them. As I mentioned, I think a computer is a tool rather than a hobby. If software is distributed in mass-market retail outlets, I expect it to work straight out of the box.

To get to the man pages, I have to successfully install the distribution, the operating system has to boot and the graphics-card driver has to make them show up on the screen. To use newsgroups and Web sites, I also have to get a modem working, find a browser and newsreader, set up my Internet connection and print out the help files or Web pages as a guide for tweaking the configuration files.

The systems

I have a PC from a manufacturer that went out of business. All of the hardware supposedly had Linux drivers for it. Windows 95 ran on all systems with no problems (except for the expected total catatonia when I swapped motherboards).

SUBHEAD2: Internal on all systems

Two CD-ROM drives — the original Toshiba and a newer Sony CD-burner (on the same IDE cable with the Toshiba as master); hardware fax-modem card; Adaptec SCSI card; Sound Blaster; SIIG CyberParallel dual expansion board; 30-gigabyte and 6-gigabyte hard drives (on the same cable, with the 6-gigabyte as master). Each drive has space for Linux: 1 gigabyte for swap on the 6-gigabyte drive and 14 gigabytes for the Linux installation on the 30-gigabyte drive.

SUBHEAD2: External on all systems

OKIPAGE 6e parallel-port printer; ancient SCSI UMAX S-6E scanner; SCSI HP Photo scanner; and a parallel-port Zip drive. The computer has a USB port, but I have nothing that uses it.

  • System 1: My original 1998 266-MHz Pentium-II with 128 megabytes of RAM and Rendition Verite 1000 video card. Neither distribution I tried (SuSE 7.1 and Mandrake 8.0) could produce a post-installation GUI, and Mandrake killed Win95. I got a blank, black screen or, if I was lucky, a text-only interface.
  • System 2: System 1, plus an ATI video card. I dumped the CDs and manuals in tOSG's cubicle — along with some vile comments about the ancestry of Tux — after the System 1 debacle. He had to do something to keep me from dashing back into the clutches of Microsoft, so he loaned me the ATI video card.
  • System 3: System 1 with a new video card based on the SiS300 chipset. There would be a slot shortage on my new motherboard, and I wanted to make sure the new card was working before swapping motherboards. I was surprised at the difference a change of video boards made in the Linux installation. Not all of it was for the better.
  • System 4: AMD K6-500, 256 megabytes of RAM and the cards from #3 (with a new motherboard).
  • System 4.1: I bought a new monitor for system 4. The degaussing controls on the old one failed, and it degaussed continually.

What almost always worked

The modem. All but one distribution with an operable GUI was capable of configuring a hardware modem and connecting to the Internet. There was one I didn't try to configure. One distribution thought it couldn't connect, but it was mistaken.

SUBHEAD2: What almost never worked

The printer. It is a non-PostScript OKIPAGE 6e running as an HP LaserJet4 under Win95, but only some of the Linux distributions could do more than make its lights flash. Annoyingly, most of the configuration routines would correctly spot the printer at first but then fumble the information into the bit bucket as soon as I clicked "Yes." Then I would have to manually select it.

SUBHEAD2: What didn't work as well as it should have

The video cards. I had well-known, mass-market video cards with chipsets that were allegedly supported, but getting a GUI to show up was never a sure thing.

More Stories By Tsu Dho Nim

© Tsu Dho Nimh. Tsu Dho Nimh is a long-time technical writer whose hobbies include gardening, herbal medicine and poking geeks with sharp sticks. Nimh has worked with almost every OS and editing tool on the planet -- from mainframe to Mac, troff to FrameMakerSGML -- and is currently writing installation and user manuals for large diesel-powered compressors for firefighting vehicles and datasheets for the next generation of high-speed CMOS12 I/O cells (not at the same company, of course).

Comments (16)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


IoT & Smart Cities Stories
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
Chris Matthieu is the President & CEO of Computes, inc. He brings 30 years of experience in development and launches of disruptive technologies to create new market opportunities as well as enhance enterprise product portfolios with emerging technologies. His most recent venture was Octoblu, a cross-protocol Internet of Things (IoT) mesh network platform, acquired by Citrix. Prior to co-founding Octoblu, Chris was founder of Nodester, an open-source Node.JS PaaS which was acquired by AppFog and ...
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Cloud-enabled transformation has evolved from cost saving measure to business innovation strategy -- one that combines the cloud with cognitive capabilities to drive market disruption. Learn how you can achieve the insight and agility you need to gain a competitive advantage. Industry-acclaimed CTO and cloud expert, Shankar Kalyana presents. Only the most exceptional IBMers are appointed with the rare distinction of IBM Fellow, the highest technical honor in the company. Shankar has also receive...