Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!mailrus!uflorida!stat!sun13!sun8!nall
From: nall@sun8.scri.fsu.edu (John Nall)
Newsgroups: comp.os.minix
Subject: Re: p.c for Minix (more(1) replacement)
Message-ID: <300@sun13.scri.fsu.edu>
Date: 24 Jul 90 19:06:21 GMT
References: <1990Jul23.011015.15237@jarvis.csri.toronto.edu> <28577@bcsaic.UUCP>
Sender: news@sun13.scri.fsu.edu
Reply-To: nall@sun8.UUCP (John Nall)
Organization: Supercomputer Computations Research Institute
Lines: 24

In article <28577@bcsaic.UUCP> paula@bcsaic.UUCP (Paul Allen) writes:
>In article <1990Jul23.011015.15237@jarvis.csri.toronto.edu> wayne@csri.toronto.edu (Wayne Hayes) writes:
>>Here is p(1) for Minix.  It is a simple replacement for more(1), because
>>I'm sick of the long delay it takes more to start up.  Has anyone else
>>wondered why such a simple program takes so loooong to start up?  Sheesh.
>
>I used to see this kind of behavior back in 1.5.2.  There was a bug 
>someplace that caused the buffer cache to thrash if you tried to 
>read a file that was larger than the cache.  (Or something like that.
>I didn't actually track down the bug.)  More(1) takes less than a 
>second to start up under 1.5.10, but it took many seconds under 1.5.2.
>

There is a nagging memory that the behavior back in 1.5.2 etc was 
cured (for me, anyway) with a chmem of something.  Perhaps "more", I
dunno.  (General rule for Minix novices: try a chmem!)  When I fixed
it, it cured several things.



--
John W. Nall		| Supercomputation Computations Research Institute
nall@sun8.scri.fsu.edu  | Florida State University, Tallahassee, FL 32306
     "Los dioses eran computadores.  ?Que otra cosa podian ser??"