> MGK> _Why_ do the a set of similar questions always come up? Doesn't
> MGK> this suggest a weakness in the Majordomo package? Is it not wary
> MGK> enough of it's environment? Shouldn't it check the permissions of
> MGK> the files and directories when it cannot access a file etc etc?
>
> Because Majordomo isn't a simple package, no, no, and no. A person
> installing Majordomo should read *all* of the documentation, including
> the FAQ; this would eliminate about 90% of all the repeated questions
> seen on the list. Of the remainder, many are OS-related issues which
> Majordomo cannot even begin to deal with internally and correcting them
> should not be it's domain.
Agreed. But maybe reporting them better might be done.
>
> MGK> A lot of the work that David seems to do would be solved it there
> MGK> was a patch set for Majordomo which fixed the largest pitfalls -
> MGK> and a lot more of his work could be avoided if Majordomo was a
> MGK> little more defensive ...
>
> No, but life in general for him and everyone else would be much nicer if
> people actually read the documentation *before* attempting to install
> Majordomo.
>
> Richard Pieri/Information Services \ Make your mark in the world, or at least
> <ratinox@unilab.dfci.harvard.edu> \ spray in each corner. -A cat's guide to
> http://www.dfci.harvard.edu/~ratinox \ life
>
Again agreed. However I read the README and the FAQ and this list
for a while first. It wasn't so much the lack of available information
as the, um, concise brevity of it that I found difficult to deal with.
I still needed help. And many of the problems I had in getting Majordoo
running actually had little to do with Majordomo itself. Examples are
a) 1.93 doesn't work with perl4.36 on Digital UNIX 3.2a, b) sendmail
barffed on me well before I even got to wrapper never mind any Majordomo
code, c) a sometimes reality challenged keyboard/chair interface. That
last happens to all of use from time to time.
But hey, what do you want for free? I didn't see an 800 number for
tech support in the README. So it has the odd bug. It has fewer than
most of the products I buy and often has a much better technical
assistance facility; this list.
True, the same questions get answered all the time. Are you
volunteering to rewrite the README or add to the FAQ?
----------------------------------------------------------------------------
Chris Johnson Internet: johnson@chaos.dac.neu.edu
Assistant Director, Systems BITNET: johnson@nuhub
Division of Academic Computing Voice: 617.373.3300
Northeastern University, 39 RI FAX: 617.373.8600
360 Huntington Ave.
Boston, MA., U.S.A. 02115
----------------------------------------------------------------------------
Follow-Ups:
References:
-
Re: Problmes
From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
|
|
