🚀 go-pugleaf

In article <1992Apr5.161632.24963@murdoch.acc.Virginia.EDU>, smb3u@kiptron.psyc.virginia.edu (Steven M. Boker) writes:
|> In article <264@moene.UUCP> toon@moene.uucp (Toon Moene) writes:
|> >In article <giDLiB2w165w@midiline.la.ca.us> dylan@midiline.la.ca.us  
|> >(Comrade D) writes:

....

|> >This is horrible.  As the NeXTanswers item says (paraphrased): "if a long  
|> >running process [like the WindowServer - TM] is adding another page to the  
|> >swap file, it can not be truncated EVEN IF ALL INTERMEDIATE PAGES ARE  
|> >FREED".  Well, there you have it.  And we thought we got a hot new OS  
|> >architecture at hand in our lovely black boxes.  EVEN VMS CAN DO THIS  
|> >BETTER.   
|> >
|> 
|> This is in fact horrible.  And I was doubly horrified to hear that 3.0
|> was not intending to address the _Number_One_Weakness_ of the operating
|> system as perceived by the users here.  Having to reboot your machine
|> several times a day under what my users consider to be "normal" conditions
|> is, to them, a considerable inconvenience.  Why NeXT hasn't put major
|> effort into this achilles heel is beyond me.
|> 
|> Steve
|> 

I fail to see why this is so awful. If you specify a "hiwat" mark so that
the swap file cannot fill the whole partition, you have basically turned
the swap file into a swap partition. We use a lot of swap on our system,
and on the SPARCs we need to set aside 300MB as a separate partition,
whereas on the NeXT, we can at least sometimes use that space...

-- 




			Magnus Nordborg
			Department of Biological Sciences
			Stanford University
			Stanford, CA 94301-5020
			USA
			(415) 723-4952
			magnus@Kimura.Stanford.EDU