I'm writing article for Destination z -- http://destinationz.org/ -- giving tips for reporting problems to vendors.
I'll include information/procedural aspects (e.g., technical details to provide, how to set severity/priority, what to realistically expect from support, collaborative debugging, dealing with sensitive installation information, problem tracking, how/when to follow up, escalation techniques) as well as communication tools to use, such as online access, file transfer, telephone, face-to-face, carrier pigeon, mental telepathy, and wishful thinking. Operating system-agnostic tips will be most valuable, though include any system-specific issues/tips/tools that come to mind. Tips are more valuable than anecdotes, though positive/negative experiences definitely add color! As usual, please copy me directly so I don't miss responses in list digests. Thanks! -- Gabriel Goldberg, Computers and Publishing, Inc. [email protected] 3401 Silver Maple Place, Falls Church, VA 22042 (703) 204-0433 LinkedIn: http://www.linkedin.com/in/gabegold Twitter: GabeG0 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
