Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!snorkelwacker.mit.edu!mit-eddie!media-lab!lacsap
From: lacsap@plethora.media.mit.edu (Pascal Chesnais)
Newsgroups: comp.sys.next
Subject: Re: Has multi swapfile bug been fixed?
Summary: No, it still looks broke...
Message-ID: <5197@media-lab.MEDIA.MIT.EDU>
Date: 12 Feb 91 00:30:39 GMT
Sender: news@media-lab.MEDIA.MIT.EDU
Lines: 21

In article Has multi swapfile bug been fixed?
 jacob@gore.com (Jacob Gore)
of : Gore Enterprises writes:
There was a bug in 1.0 that prevented people from using multiple swapfiles.
Has it been fixed in 2.0?

[The following is an excerpt from NextAnswers QA355, as you can
see they still think the bug is there -- pasc]

This will enable paging to two files (based on the standard
configuration of swaptab):

	/private/swapdisk/vm/swapfile
	/private/vm/swapfile

This might seem like A Good Thing, but it isn't.  Last we knew,
there was a (minor?) bug which prevented using multiple
swapfiles successfully.  (The bug is that if a mapped file spans
swapfile boundaries, not-completely-predictable things can happen.
To tickle the bug, though, the primary swapfile must fill
up first.)  Should be benign, really.