From Windows to a Debian GNU/Linux desktop, sans the geekness
The Original - since June 2006 - Run Debian GNU/Linux and be Happy.
Keep those old computers. Debian (Linux) will run happily on your 8 year old computer. No GUI or light desktop environment like Fluxbox - you'll be surprised and save beaucoup loot.
 

this site  web    
The Goods
Home Page
Forum
debiantutorials.org Licensing
Website Disclaimer
Site Map
Links
w32codecs
How to really switch Mom to Linux
Documentation
Release Notes
Developers Reference
Debian Survival Guide
Debian Books
Manuals
Debian Security
Linux Dictionary
Leaving Windows
Resize Windows Partition for Dual-Booting
Back up your Partitions, Imaging
Still Suffering Windows
Keep your Money, your Sanity and your Self-Respect
Installing Debian Etch
Debian GNU/Linux (Etch) Installation Tutorial
My Etch Desktop in 150 words or Less
Upgrade Sarge to Etch
Configure Debian Etch
Multimedia on Debian Etch
Install nVIDIA 3d driver on Debian Etch
Wireless on Debian Etch: Broadcom - bcm43xx
Klikit, Klikit good
Handy Little Things
Package Management
Peripherals & Debian Etch
Set up your web cam on Debian Etch
Printing in Debian (Browsers, too)
Your ipod on Debian Etch
Atheros Wireless
Broadcom Wireless
Etch on the Desktop
Visitors apache log reader
Andrea del Sarto
(Poetry snippet for your Ignorant Ass)
Beagle on Debian Etch
Convert Digital Camera .mov Files
Some Debian Etch System Files
My Debian Desktop
Using wget
Copying or Ripping DVD's in Linux (Debian)
Reset root password
So, you want to run Linux
Convert mov files
Securing Debian
Password Protect Grub Boot Loader
Debian Etch as Server
Debian Linux file and print server: NFS, CUPS, LPR
Stream your music with gnump3d
Simple local web server on Etch
Web Server on Debian Etch
Miscellaneous Linux
Linux Conventions
Can People read my Documents?
Install Software on your Linux System (Debian)
Partition your Hard Drive
History of debiantutorials.org
A School Without Windows (PDF)
How to talk to Tech Support
Linux Demystified
Off Topic
A DRM Dissertation
An Artist's take on Downloading Music
An Insane and Damaging lack of Understanding
On Children and Drugs
On Visitor Q
Intellectualism for the Masses
debiantutorials.org stats
Smart Crows
How old are We?
Why we run Debian
How not to ask an egomaniac like myself for an article
Sarge Specific Tutorials
Installing Debian Sarge, net install, no DHCP
Easy Graphical Sarge Installation Tutorial
Rebuilding my Debian Sarge Machine
Multimedia for Sarge
w32codecs
nVIDIA on Sarge
Trouble Burning discs: cdrecord
Athcool on Debian Sarge
Where are my Newly Installed Apps?
Easy LAMP on Debian Sarge
Archive
Sites Worth a Look
Debian Mailing List
spidercider
Linux Comparison at PolishLinux.org
Thin Clients
Common Commands
Common iptables Filtering
iwouldntsteal.net
Big-Ass iptables info Page
iptables Port Reference
README: Firewall
General Security Tips
Newbie Security
Kickass RFC's
Data Breaches
Hemp Seed Oil
linux-hardcore.com
Search for a local Computer Tech
Evelyn's Linux Cheat Sheet
Lotsa (687) Linux Commands

Favorite Utilities

Super Grub Disc
System Rescue Disc
News Feeds
visitors run
operating system
Linux
Windows
Mac
Unknown
BSD
54.8 %
39.8 %
3.40 %
1.50 %
0.10 %

web browser
Firefox
Mozilla
IE
Opera
Epiphany
41.4 %
25.1 %
15.8 %
8.40 %
3.50 %
updated 17apr08
What's Root?
Root is the super-ultra-mega. All system commands on a Linux box need to be done as root. This means installing software and changing files not in your /home directory, etc. In your terminal, if you're logged in already become root by typing su at your $ prompt, then the root password. Log in the system directly as root from a terminal, but not the graphical login. # shows root.
dediantutorials.org is ad-free
debiantutorials.org has always been and will always remain ad-free I make no unrealistic demands that you "owe me for my time and bandwidth" in order to use my site. I detest all those scumbags out there that think that they are owed something for putting a web site up. I do debiantutorials.org because I love it. You owe me nothing.
If you can walk and chew gum at the same time, you can run Linux

    Friday, May 09, 2008      Contact  Etch Info  what's new in Etch  Linux Demystified  Our Forum
How to talk to your technical support PDF Print E-mail
Written by machiner   
Sunday, 15 July 2007
When you have a problem on your computer it can be frustrating. Especially if you don't understand the error, or what's going on. Something that worked fine even 2 hours ago can make you crazy if, for no apparent reason, it just fails out of nowhere the next time. Or, you're in Linux now and something that "worked fine" in Windows is giving you trouble. Nobody knows frustration more than tech support or admin. And, like most things in life this frustration on either side can be avoided very simply.

Understand that as your technical support or your admin -- we really want to help you. Really. We are admins, tech support. We love this stuff and every opportunity to assist is an opportunity to ourselves learn more. Like anyone else we may take things for granted and skip on some things. It's nice to relearn something we may have forgotten, or get the chance to do a thing again that suddenly we need to know cold. It's nice to feel like we're enabling as well.

Just like you we are regular people, no dumber or smarter -- no less or more a tolerance threshold. We just happen to like technical things. Most of us enjoy helping you that simply don't like technical things. What we don't like is helping the same person do the same thing. Or fixing the same problem. Or trying to decipher the gibberish coming from the other end of the phone. Like you we need some clarity. There has to be a level of communication and it doesn't mean that anybody has to learn some other language or goto tech school or anything like that. It just means that the same basic aspects of communication need to be established in order to solve a problem. This is where it gets difficult. People think computers are magic. People think that computers are smarter than them or really fragile. No, no and again no.

When you have a problem on an otherwise stable computer the issue can very often be traced back to user-error. The thing about this is that Humans have an ego. EGO. Troubling to deal with. Humans like to appear smart and sophisticated, error free. When the fact of the matter is as I have described -- people generally are in a state of perpetual D'uh when it comes to anything "computer". There is trouble when a person may report that they were "using Google" to check their checking account balance. Or, "I tried to print but the message kept saying 404 error". When we are engaged with this sort of problem and cannot find a common ground for communication then the problem quickly escalates into a thing that never should have been.

Computers are not magic, you're not an idiot and we need to be a whole lot kinder to each other.

Just be clear. Report what's really happening and what you really did. It's useless to beat around the bush or fail to understand basic terminology...like: plug, mouse, window (not the OS, dammit!), address bar, desktop, browser, alt+tab. Google is not your computer, the "thingy" is a descriptive term which means absolutely nothing. I like this one, when an admin has asked you to open a tool or program, it's nice to let them know that it has actually opened. I've been in countless discussions with otherwise well-meaning people that would have been 10 minutes shorter had they only reported, "OK, that's opened".

We grow weary of trying to communicate with "Ashley the mid-wife" because she's confounded by a thing that sits idle until instructed, her computer scares the hell out of her. It's irrational. Tech support folk are flabbergasted as to why Ashley cannot understand that Internet Explorer is a web browser. I did just get off the phone with "Ashley" and I'm in a fog as to how she can remember to turn the stove off when she's done cooking. She raised 4 kids, all kind and bright adults. She graduated 4th in her class.

Ashley, brightest star in the heavens, you're killing me. When you call me I want to help you but I can't because you fill my head with gobbleygook and you get frustrated when I have absolutely no clue what you're doing. You can't tell me because you don't know how to tell me and you refuse to accept that I can't help you if you can't tell me what's going on.

Some of us are good at giving directions and some are not. Some of us are confident people and well, some of us are afraid of our own shadows. Some of us flat-out refuse to learn anything that we didn't already in grade-school. Yet, we (you) will demand that your admins or tech support have ESP and you are appalled that we can not decipher what you are trying to say. Well, you have to understand, the onus is on you to explain what's happening or what you did, or didn't do.

When you initiate a dialog with your admin, or tech support, you must realize that you are wanting a resolution. You have a problem. You demand satisfaction. Therefore it is important that you are able to be clear and precise that you may get your satisfaction. State the problem. You should not report:

"This computer sucks, it won't do anything!"

When you do, you will immediately lose us. Your computer does not suck. It cannot read your mind. Some programs and operating systems have limitations. Hardware has limitations. There are restrictions at play sometimes, sometimes you don't have the necessary software installed to accomplish the task you want. There are many reasons why you cannot do what you want, but the most obvious reason is usually that you are doing it wrong, or you simply don't know how. This is OK -- because you are not born with an inherent ability to do or operate a thing. However, it's not OK when you expect magic from a box that is simply a dumb thing waiting for you to tell it what to do. You must at least learn the basics.

Like you, we are Human. We like to be addressed accordingly. We like to employ the same common politeness that is expected in society and we expect others to as well. Try this when initiating a conversation with your support: "Hi." It's a good start. You don't have to ask us about our children or get warm and fuzzy -- just say "Hi". Next you should try to be honest about what's happening on your machine. Don't say, "All I did was...." No. That won't do. Try to explain what you want to do, and then try to explain how you went about it. Use appropriate descriptors or terminology. Try to get the support to know where you are and what you're looking at. Say things like, "I'm in my browser", or, "I'm on my desktop". Even, "Word won't cooperate" is much better than saying "I can't print!!!" Well, what are you printing? What program are you in? What was the last "thing" that you installed?

Your support really does want to help you. However, it is your job to allow this to happen. You must let us help you, and you must communicate clearly in order to solve the problem.

Also, see this thread for more insight.

--machiner 16 July 2007





Reddit!Del.icio.us!Facebook!Slashdot!Netscape!Technorati!StumbleUpon!Newsvine!Furl!Yahoo!Ma.gnolia!Free social bookmarking plugins and extensions for Joomla! websites!
Trackback(0)
Comments (0)Add Comment

Write comment

security code
Write the displayed characters


busy
 
Creative Commons License © debiantutorials.org Thanks for dropping by. I hope you have found this site to be helpful.   Search for a local Computer Tech  debiantutorials.org