From: seidl@alw.nih.gov (Edward Seidl) Subject: Re: Fonts not compressed, oopps Date: Mon, 22 Feb 1993 11:14:09 GMT
In article <1993Feb21.043446.22236@random.ccs.northeastern.edu> mirons@ccs.northeastern.edu writes:
> The README that sits on tsx-11.mit.edu says they are allready
>compressed. As this is the README that people will be installing from
>the package is wrong. Linux has enough problems with library
>compatability, etc. without having to get to the install README by
>installing the package.
[...]
> A package with multipule, and conflicting README/install instructions
> is poor programming, and unfortunatly very typical of linux (as a
>whole system) these days.
Later,
In a previous article, mirons@ccs.northeastern.edu (Michael A. Irons) says:
> Linux should not be a system you have to be a hacker to use,
>but a system you can hack. This is the only other free unix available
>and you can't expect put up a sign 'unix gurus only need apply, all
>else put up, or shut up'. There are alot of people here who's first
>exposure to unix will be Linux, or BSD. There's nothing you can do
>about it, it's free and people are going to come here first. You can't
>expect everyone to know how to use this, and they are asking
>questions. Making things simpler keeps the COL traffic down, and
>that's something everyone would like.
>
> Recently people on COL have developed am attitude that'll kill
> off Linux real quick. I tried to point out an inaccuracy in a major
> package and got: [ assorted flames ]
Ok, what started this off was a fairly snotty (sorry, but that's the way
it comes across) announcement that the documentation is wrong. Ok. Fine.
Let others know about it, but try to be polite. Saying other peoples'
hard work is "poor programming, and unfortunatly [sic] very typical of linux"
is rude. Plain and simple. I think you deserved most of the flaming you
got. (Criticizing spelling is pretty lame, though.)
Remember, linux is FREE.
Second point. Linux is still alpha. Don't expect everything to work as
advertised. And if something doesn't work the first time, go back and read
all the documentation you can find on the package. If you still have problems,
or if all the documentation is wrong, then tell the community. But please
be polite about it.
From : crd6@po.CWRU.Edu (Chad R. Dougherty)
> Thank you very much for this reply. Although I myself haven't seen
> this attitude much in this newsgroup (I'm relatively new), I have seen it
> elsewhere and it made me angry. What did these same people who rip on
> others now do when they needed help with something?
My guess is they read TFM :)
-- Edward Seidl DCRT/CSL Bldg 12A, Rm 2033 seidl@alw.nih.gov NIH, Bethesda, MD 20892I'm not paid enough to have an opinion, much less express one for my employer.