Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!sun-barr!ccut!titcca!cc.titech.ac.jp!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.arch
Subject: Re: Fast /tmp (was Re: Mixing paging and IO is inefficient)
Message-ID: <5755@titcce.cc.titech.ac.jp>
Date: 3 Jul 90 07:00:54 GMT
References: <499@garth.UUCP> <5660@titcce.cc.titech.ac.jp> <137770@sun.Eng.Sun.COM> <691@sibyl.eleceng.ua.OZ> <5694@titcce.cc.titech.ac.jp> <63090@lll-winken.LLNL.GOV>
Sender: news@cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 26

In article <63090@lll-winken.LLNL.GOV>
	casey@gauss.llnl.gov (Casey Leedom) writes:

>| Do you know ex3.7preserve? We should try fsck and fsck -y before newfs.

>  No longer relevant.  Under the new directory organization /tmp is supposed
>to be used for truly transient files like compiler temporaries, etc.  /usr/tmp
>is supposed to be used for more important files like editor temporaries, etc.

That is a good news also to me.

>Berkeley has already implemented a Memory File System and mount /tmp on it by
>default.

Memory disk (even virtual memory disk) has several fundamental defects.

Judging from the previous USENIX, Berkley's memory disk inherites the
property that sometimes:

	Real disk faster than RAM disk

which was the original subject:

Why do you use memory disk if it is slower then real disk?

						Masataka Ohta