Xref: utzoo comp.unix.xenix:11380 comp.unix.i386:4754
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!munnari.oz.au!metro!johnt
From: glenn@extro.ucc.su.OZ.AU (Glenn Geers)
Newsgroups: comp.unix.xenix,comp.unix.i386
Subject: Re: Using GCC/GAS Xenix on AT&T Unix V/386.3.2
Message-ID: <1990May4.044536.12962@metro.ucc.su.OZ.AU>
Date: 4 May 90 04:45:36 GMT
References: <1990May2.220056.25855@kth.se>
Sender: johnt@metro.ucc.su.OZ.AU (Louise Rowling(see rossc))
Organization: Uni Computing Service, Uni of Sydney, Australia
Lines: 19

From article <1990May2.220056.25855@kth.se>, by perand@admin.kth.se (Per Andersson):
> 
> Swapping is when you move whole processes in and out of memory, paging when
> you move parts (pages). This is my favourite bashing of System V contra BSD.
> System V up to and including 3.2 doesn't have paging ! The most recent trouble
> I had with this was when installing the brand new 386/ix on my machine. 
> I found some nice things not in the kernel, and added support for them, but no,
> there was to little memory to run them. Then I tried to build a new kernel,
> like the original one - bang. The linker process was to big to fit in memory 
> at the same time as the OS, so it wouldn't build. Yawn..... Of course I could 
> have read the manual but...
> Now does anybody really know if Xenix/386 can do paging ?

As far as I can tell it *really* does demand page. Take a program that accesses
more than phys. mem - kernel mem (A simple array clear/fill program is good 
here) and run it twice. On my machine both processes complete albeit slowly and
vmstat -s shows pagein/pageout to the swap area go up nicely. I have also had
gcc blow out to over 4 Mb of data (all that shows up on ps) without complaint.
									Glenn