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.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide