🚀 go-pugleaf

In article <1992Sep23.195218.25904@ornl.gov> woo@ornl.gov (John W. Wooten) >  
20)  I had a line in /etc/crontab to do an updatedb every night.  this  
> used to prepare a way so that find filename would very quickly give me  
> a path to that filename.  It doesn't work any more.  I can't tell that  
> crontab is getting done.  I checked and its still there and cron is  
> running.
> 

This is a problem with the new version of find, which no longer has the "fast  
find" capability in it.  What I find particularly humorous is that  
/usr/lib/find is still present and /etc/find.codes (the find database) can  
still be found in /usr/bin/find using "strings -8".  The fix is to replace  
with a non-broken find, such as the GNU find [which is much nicer than the  
original find in any case].

By the way, a number of people have reported that their NeXT computers were  
launching much slower under the new OS.  As far as I can tell, this seems to  
be a consequence of running NS3 on machines with too little physical memory.   
I have noticed no observable degradation in performance on any of my local  
machines, but they all have at least 20 MB of memory...

Carrick Talmadge
clt@physics.purdue.edu