A *lot* of you responded to my query about the mechanics and operation
of this mailing list. It's taken me several days to turn all those
responses into this summary, because while there was a general consensus,
there were a lot of diverse points of view expressed.
The consensus seems to work out to something like this:
Don't ask for help if you're not willing to give it. That doesn't
mean that junior people are expected to try to answer complex
questions that challenge senior people; it means:
- that anyone asking a question should "play by the rules"
as expressed in the FAQ and be sure to summarize the responses
for everyone's mutual benefit.
- that in a few years, when those people are more experienced,
they should return the help they were given by helping those
who are just starting out.
- that nobody should be bothering the list until they've exhausted
other resources. Resources frequently cited are:
(1) the manuals (RTFM!)
(2) the Sun-Manager's FAQ
(3) the various Usenet FAQ's
(4) the README file that came with the software package
(5) the AnswerBooks
(6) browsing/searching the Sun-Manager's archive
(7) searching the SunSolve web site
(8) using a web searching engine like Alta Vista and
a couple of relevant keywords.
- that anybody who *doesn't want to "play by the rules"
as expressed in the FAQ is on their own -- of course,
they're free to start their own Sun-Manager's mailing list
with their own rules.
- that, judging from the responses I received, open-ended queries
like "How do I set up NIS?" are the least likely to receive
answers, because they indicate no effort on the part of the
person posing the question. Specific questions ("I have done
X and Y and Z, I am observing A and B when I think I should be
observing C, what might be wrong?") are much more likely
to receive friendly answers.
- that incomplete questions (don't mention which version of
the OS, which hardware platform, which version of a 3rd-party
package, etc.) usually cause at least one extra round of email
-- or -- cause people to ignore the question.
- that people in a position to answer questions don't seem
to have a problem with inexperience (on the part of the people
asking the questions) but they do have a problem with laziness.
(This ties in to the list of resources above, but it was mentioned
often enough that I figured it deserved its own listing.)
- that opinions were split on how to respond to queries such
as that posed by Mr. Glass. There were roughly three viewpoints:
(a) ignore them (b) don't answer them and point them at the FAQ
or (c) answer them and point them at the FAQ. Most of the
folks thought (a) or (b) were the right options. Many people
commented that they noticed which folks didn't "play by the rules"
and were in the habit of (a).
- that the more experienced people are, the less tolerant they
are of folks' infractions of the "rules". (I can understand
this; back in the Olde Days, running Unix meant you got a tape,
a 2-inch stack of manuals, and Bell Lab's best wishes. No
FAQs, no mailing lists, no books, no newsgroups, no web, nothing.
Many of us are completely delighted to have a resource like
this and don't want to see it become non-useful.) (And we had
to run our machines with coal. And we were shackled in dark,
damp cellars with only the burning of old RSTS and VMS manuals
for heat and light... ;-) )
Anyway, I'd like to thank *almost* everybody for responding, especially
the people who disagreed with my initial opinion and took the time to
make cogent arguments for other points of view. You've given me plenty
to think about.
I say "almost", because I'd like to extend special recognition to the
person who decided that it would be appropriate to avoid answering
the question and instead take a few potshots at my religious and
ethical values, or lack thereof. Not a good idea, especially when
you're dealing with someone who survived the Mark Ethan Smith flame wars
on Usenet back about a decade ago. :-) In an attempt to adopt some
of the "kinder, gentler" suggestions which arrived, I declined to
respond, and just ignored it. This time. Now you all owe me a cookie
(raisin-oatmeal, please) for being so patient. ;-)
---Rsk
Rich Kulawiec
rsk@itw.com
Folks who contributed (in alphabetical order):
----------------------------------------------
Bill Reed <reedwv@stp.xfi.bp.com>
Bob Woodward <bobw@kramer.filmworks.com>
CO Thomas Esser(101) <thomas@jetson.usi1.com>
Claus Assmann <ca@informatik.uni-kiel.de>
Dan Pritts <danno@fv.com>
Daniel Lorenzini <lorenzd@gcm.com>
Gary Lee <rgl@xdiv.lanl.gov>
Herbert Wengatz <hwe@uebemc.siemens.de>
James Cayz <cayz@del-aware.lib.de.us>
Jim Harmon <jim@telecnnct.com>
John D Groenveld <groenvel@cse.psu.edu>
Keith.Willenson@sunny.health.state.mn.us (Keith Willenson)
Kevin P. Inscoe <kpi@hobbes.crc.com>
Kevin.Sheehan@uniq.com.au (Kevin Sheehan {Consulting Poster Child})
Marcus Pless <mpless@ljswc.ucsd.edu>
Mark Belanger <mjb@ltx.com>
Michael R. Zika <zika@oconto.tamu.edu>
Mick Morgan <maillist@ccta.gov.uk>
Rachel Polanskis <rachel@juno.virago.org.au>
Ray Brownrigg <Ray.Brownrigg@isor.vuw.ac.nz>
Wanda Perrier <PERRIEW@ex1.wes.army.mil>
ahill@lanser.net (Alan Hill)
applix!cobra!charles@uunet.uu.net (Charles Homan [ext 422])
bleary@state.ma.us
blymn@awadi.com.au (Brett Lymn)
brian@chimera.psych.unimelb.edu.au (Brian Desmond)
celeste@celestial.stokely.com (Celeste Stokely)
davem@solve.net (Dave McFerren)
edd@acm.org (Edgar Der-Danieliantz)
foster@bial1.ucsd.edu
fpardo@tisny.com (Frank Pardo)
gcarr@lanl.gov (Gary Carr)
glenn@atm.ch.cam.ac.uk (Glenn Carver)
iv08480@issc02.mdc.com (Colin Melville)
jjr2@edi-nola.com (Jack Reiner)
john@tdi.com (John)
jwf@ccuc.on.ca (John W. Funk)
kwong@scis.acast.nova.edu (James Kwong)
manderso (Mark S. Anderson)
manderso@neon.mitretek.org (Mark S. Anderson)
martin@mednuc.hsr.it (Martin Achilli)
nina@tumble.com (Nina)
obryhimk@gecmc.gecmc.ge.com (Kerry O'Bryhim)
raju@hoho.ecologic.net
springer@aitsun500.tci.com (Jerry Springer)
szh@zcon.com (Syed Zaeem Hosain)
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:17 CDT