Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pacbell!sactoh0!bfbreedl
From: bfbreedl@sactoh0.UUCP (Bob F. Breedlove)
Newsgroups: comp.lang.c
Subject: Re: GROK THIS!
Summary: Grok "Grok"
Message-ID: <576@sactoh0.UUCP>
Date: 4 Dec 88 22:51:31 GMT
References: <0XZeQod38k-0MSz0V7@andrew.cmu.edu> <9046@smoke.BRL.MIL> <9058@smoke.BRL.MIL>
Organization: Sacramento Public Access, Ca. USA
Lines: 17

In article <9058@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn ) writes:
> In article <575@sactoh0.UUCP> bfbreedl@sactoh0.UUCP (Bob F. Breedlove) writes:
> I lost track of the original reference, but I thought that the term
> came up in the context of an advisory message ("now trying to see if
> You mean to tell me that there is a qualified system manager who
> 
> Your point about jargon obscuring understanding is well taken, though.
> It's something designers and implementors should be more aware of.

There is obviously at least one who doesn't read science fiction,
didn't go to school at a university that supported UNIX, or for
some other reason doesn't know what "to grok" is, otherwise we
wouldn't be having this discussion!

-- 
Bob Breedlove  SYSOP: BOBsBBS (916/929-7511)
        pacbell!sactoh0!bfbreedl