Return to BSD News archive
Xref: sserve comp.os.linux:47656 comp.os.386bsd.questions:3743 comp.windows.x.i386unix:2459 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!indyvax.iupui.edu!ibol500 From: ibol500@indyvax.iupui.edu Newsgroups: comp.os.linux,comp.os.386bsd.questions,comp.windows.x.i386unix Subject: Re: SUMMARY: 486DX2/66 for Unix conclusions (fairly long) Message-ID: <1993Jul12.122259.1409@indyvax.iupui.edu> Date: 12 Jul 93 12:22:59 -0500 References: <21k903$3q4@GRAPEVINE.LCS.MIT.EDU> <PCG.93Jul12003233@decb.aber.ac.uk> <CA0zHp.CqK@unixhub.slac.stanford.edu> <21qfam$htg@theory.TC.Cornell.EDU> Lines: 15 > Someone correct me if I'm wrong, but Linux "swapping" is really "paging" to > the hard drive. As far as I know images are not "swapped" to disk or > rendered inactive; the "swap space" is actually used as "paging space". > Therefore, calling it "swap" is probably a misnomer. For the record, Linux features "virtual memory using paging (not swapping whole processes) to disk: to a separate partition or a file in the filesystem, or both, with the possibility of adding more swapping areas during runtime (yes, they're still called swapping areas). A total of 16 of these 16 MB swapping areas can be used at once, for a total 256 MB of useable swap space." ( quote from the Linux info-sheet ). Later, Andy Strain