Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!uxg.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu
Newsgroups: comp.sys.next
Subject: Re: NeXT --- not worth the effort (
Message-ID: <245300006@uxe.cso.uiuc.edu>
Date: 8 Feb 89 15:41:00 GMT
References: <7076@pucc.Princeton.EDU>
Lines: 25
Nf-ID: #R:pucc.Princeton.EDU:7076:uxe.cso.uiuc.edu:245300006:000:1062
Nf-From: uxe.cso.uiuc.edu!mcdonald    Feb  8 09:41:00 1989



>Not only do I get a picture of an aardwolf, but when I scroll through the meani
>ng of "zymurgy" I get all the "a" words through "abominable snowman". So it is
>only fair that I get the attached pictures as well, I guess.
>       Nick Katz

I think the aardwolf is really cute. Not nearly as ugly as a hyena.

On the other hand, a funny thing happened on the way to the aardwolf.
Somehow, we don't know how, I started the Next on the task of,
presumably, indexing the entire Webster. At any rate it chugged
away on its disks (both) for several minutes before we tried to kill 
it. But I couldn't kill it at all from the keyboard. Another
person logged in over the Ethernet as root and killed my process - 
which immediately put up a note to that effect - but continued whirring
for two minutes (cleaning up the disk?). What happened, and is there
any easier way to stop it from doing this?


Has anybody figured out why starting up the special NeXt programs
is so slow, when ordinary Unix functions and running the neat programs
is quite peppy?

Doug McDonald