One Too Many Viruses: Converting a Non-Geek to Linux, Part 1
I got a call from a friend the other day asking, "What would it take to get me a Linux box?" I could hear the frustration in her voice. This wasn't the first time she experienced computer problems. Word-based viruses run rampant on college campuses, and being on a student's budget, she can't afford the top-of-the-line AV software. On this day, it seemed that another virus had snuck past the freeware she had loaded.
We had been discussing Linux for some time. I had given her an account on my wife's machine so she could play with it, and we had talked about what it was she needed from a computer. Being a law student, she had specific layout requirements for her work but no requirements for a specific word processor. She did need Acrobat Reader, a browser that would handle various sites she needed to access for her classwork and support for her printer, a Hewlett-Packard DeskJet 697. She also wanted to be able to move files to and from her Windows machine, in case something came up that Linux couldn't handle, and to use the two at the same time in her cramped office.
The only thing I had a question about was the printer, so I fired up YaST2 on my local SuSE box and navigated the printer dialog. Both a generic 690-series driver and one specifically for the 697 were listed. Everything else I knew we could do. "So, what's your budget?" I asked. "$500", she said. Can do; I knew where she could order a machine for $200 plus shipping. "I'd like a new monitor, too", she added. Her eyesight isn't the best, and the 14" CRT on her old machine was giving her headaches. Fortunately, I had a source for good used monitors, a rather large second-hand computer store downtown.
She picked me up, and we went down the store. When we got there, a sign out front advertised, "Back To School Special - Complete System, $299". The store had received a shipment of commercial Compaq systems: 933MHz Pentium III machines in a small form factor with 128MB of RAM, a 20GB hard drive, CD-ROM, integrated graphics, NIC and sound, modem, 17" S720 monitor, keyboard, scroll mouse. Almost everything she needed was sitting right there in front of us.
I was concerned about having only 128MB of RAM, though, because KDE (the desktop she wanted) tends to take up so much space. So, we negotiated a $20 upgrade to 256MB of RAM, and we also picked up a KVM switch and cables, plus a cheap Ethernet card for her Windows machine, to facilitate Samba. We walked out with the whole shooting match--tax, tag and title--for a handful of change under $400. "Holy [censored]", she said, "I just bought a Linux box." "Well, it's not a Linux box yet", I replied, "but we'll fix that."
We brought the system back to my house, and I proceeded to put SuSE 8.2 on it. I made sure several different word processors were loaded, as well as Samba, AcroReader and the sound goodies. So far, so good. The next step was to have her walk through a demo. She wanted to make the fonts bigger, so we fiddled around for a bit in the KDE Control Center. Under Appearances and Themes: Fonts, we found where she could change the font size for all the decorations and such that KDE controlled. I also showed her how to change the fonts in Galeon, and where the zoom control was.
What lies ahead of us, however, is the truly interesting part. A lot of work needs to be done once we actually get the machine to her office. I have to make sure the machine can access her dial-up connection from a local telco. We have to set up the printer and make sure it prints nicely. We'll need to make sure the KVM we purchased doesn't confuse X; if it does, I'll have to show her how to switch virtual consoles to avoid the issue or how to fix it if it happens. And the big task will be configuring Samba and her Windows machine so they talk to each other for both file sharing and printing. I also may want to set up dynamic DNS so I can get into the machine easily on her dial-up link and fix issues. It's only a 15-minute drive, but why waste gas when you can use SSH and neither of you has to get out of your PJs? As both of us are stuck on single phone lines and dial-up connections, I've already grabbed the latest version of GAIM and compiled it for her, so we can talk and fix at the same time. SuSE 8.2 actually deals nicely with having both GTK 1.x and GTK 2 on the same machine, so getting GAIM to work simply was a matter of making sure all the relevant -devel RPMs were loaded. This isn't quite as simple as it sounds, but then that's why I'm helping her.
What I have learned so far from this process is the devil is in the details when you're dealing with someone--a friend, a client, a boss--who is brand new to Linux. The smallest thing--the ability to move icons from the task bar to the desktop or having the right kind of table in your word processor--can become a big issue. But working with new people on a daily basis and becoming familiar with all the weird and wonderful things a modern Linux system can do keeps you sharp. Helping new folks learn, be they friends, co-workers or some random person that shows up to a LUG install-fest, not only promotes Linux but is a good investment in your own skills, both technical and interpersonal. And from down here in the trenches, this is a happy thing.
Glenn Stone is a Red Hat Certified Engineer, sysadmin, technical writer, cover model and general Linux flunkie. He has been hand-building computers for fun and profit since 1999, and he is a happy denizen of the Pacific Northwest.
|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
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- What's the tweeting protocol?
- Tech Tip: Really Simple HTTP Server with Python
- Kernel Problem
12 min 28 sec ago
- BASH script to log IPs on public web server
4 hours 39 min ago
8 hours 15 min ago
- Reply to comment | Linux Journal
8 hours 47 min ago
- All the articles you talked
11 hours 11 min ago
- All the articles you talked
11 hours 14 min ago
- All the articles you talked
11 hours 15 min ago
15 hours 40 min ago
- Keeping track of IP address
17 hours 31 min ago
- Roll your own dynamic dns
22 hours 44 min 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?