[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: newbie

Is that what the "WELcome" means in Linux, do it? Charming way to be made to feel welcome. You demand I
understand you, but the compliment is not returned. Is that what happens when one gives FEEDBACK,
mentioned in every doc?

I read the intro to anaconda on redhat and NOW I get what is MADE conventional to the anaconda list. Did
I use any rude words or did you mean not stepping on your toes, pardom me? OR paying deference to you?
HOW well do you know me?

SYNOPSIS: ALL languages, cultures, specialised jargon, math, computerese are CLOSED systems in which
every word is explained by every other words INSIDE that system. That's also why win and RH don't
interact too well without a translator installed with mount. "mount" usually means "climb" but not in

FI  BUG in Windows means the PC hangs and in Linux it means it don't work as well as it can, so fix it.
BUG in computerese derives from Eniac when a bug caused a short in the battery of glass radio bulbs, by
metaphoric extension of "you bug me". BUG is slang, not proper English, which calls them insects.

Now who will HELP me with MY problem, you've been pretty loud about yours.

My currently main neurosis with Red Hat right now is which order does one do things to customise.  1st
one makes directories, then subdirectories and after that mounts certain packages, -programs, etc to
me - now HOW does one MOUNT  - which does not mean sit on the Monitor. I've read the white handbook and
all the docs on the frisbie and there one finds TOPICAL help but not in wuyhich order to proceed. The
reason for that I explained before, it's the style and convention of use in writing docs.


----- Original Message ----- 
From: "Robert P. J. Day" <rpjday mindspring com>
To: "John" <red computerdatasafe com au>
Cc: <anaconda-devel-list redhat com>
Sent: Wednesday, June 25, 2003 12:38 AM
Subject: Re: newbie

> On Tue, 24 Jun 2003, John wrote:
> > On Sun, 22 Jun 2003, Robert P. J. Day wrote:
> >
> > > On Sun, 22 Jun 2003, afme ihug co nz wrote:
> > >
> > > > Hi folks, totally new to L Rh, be warned <g>
> > >
> > > cool. then the first lesson you should learn is to use a meaningful
> > > subject line.
> >
> > Taking some care over your English wouldn't hurt either. I gave up on
> > it.
> >
> > And, pls wrap your lines at about 72 chars: a lot of us read email in an
> > 80-char window, and lines that are one and a half lines long are very
> > aggravating.
> without getting into specifics, i already got an offline blast from
> the original poster, complaining about my lack of tact or social grace
> (or something to that effect) regarding chastising newbies for a
> breach of normal mailing list etiquette.  (part of his defense was
> that i should have cut him some slack as he was a newbie.  i
> will not even get into the internal contradictions involved in
> a self-proclaimed mailing list "newbie" on an anaconda development
> mailing list. :-)
> anyway, even newbies have an obligation to understand the most
> basic rules for ML etiquette.  to wit, a short summary:
> 1) use a meaningful subject.  i have already configured my procmail
>    filter to scrap postings that say simply "help" or "urgent" (and,
>    now, "newbie" :-).
> 2) wrap lines at ~72 columns.  you may use a microsoft mailer.
>    there's no reason *we* have to suffer for it.
> 3) do not top post.
> 4) do not post in HTML.  no, this is not negotiable.  (and yes,
>    my procmail filter tosses any posting whose first line is
>    "<html>").
> 5) remove unnecessary content from your responses.  as in, be
>    brief, concise and specific.
> there's more, but this is generally considered to be a good start.
> rday
> p.s.  and why don't i use upper case?  because i was told years
> ago that unix was a lower-case operating system.  i took that
> literally. :-)
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]