Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!davison
From: davison@menudo.uh.edu (Dan Davison)
Newsgroups: comp.sys.next
Subject: Re: Those Damn Keyboards
Message-ID: <1991Feb12.042235.22476@menudo.uh.edu>
Date: 12 Feb 91 04:22:35 GMT
References: <5137@media-lab.MEDIA.MIT.EDU>
	<1991Feb8.050647.19715@menudo.uh.edu> <8007@umd5.umd.edu>
Sender: usenet@menudo.uh.edu (USENET News System)
Organization: University of Houston
Lines: 27
In-Reply-To: matthews@lewhoosh.umd.edu's message of 9 Feb 91 15:25:02 GMT
Nntp-Posting-Host: menudo.uh.edu

In article <8007@umd5.umd.edu> matthews@lewhoosh.umd.edu (Mike Matthews) writes:
>
>   >And, if you use the puked-up excuse for a network database called
>   >NetInfo you will spend a lot of time playing with that far-off "|"
>   >key to fix things NetInfoMangler throughly damages.
>
>   Let's try to keep things rational, eh?  NetInfo has YET to mess up MY
>   machine, and YOU are the only one who has complained, so I would conclude
>   that YOU screwed up somehow.
>
>   Unix boxes aren't toys.  You mess up, they mess up.


Then you will undoubtedly be startled to find out that *NeXT* (not me,
NeXT Tech Support) can't find anything wrong with the setup and
suspect a bug in NetInfoMangler in release 1.0.

It's very hard to mess up when the software doesn't work right to
begin with.  On the other hand, there is another group here at UH that
has *not* had this problem...but they are running 2.0 all around.

dan
--
dr. dan davison/dept. of biochemical and biophysical sciences/univ. of
Houston/4800 Calhoun/Houston,TX 77054-5500/davison@uh.edu/DAVISON@UHOU
Disclaimer: As always, I speak only for myself, and, usually, only to
myself.