Path: utzoo!attcan!uunet!jarthur!usc!zaphod.mps.ohio-state.edu!uwm.edu!lll-winken!casey@gauss.llnl.gov
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.arch
Subject: Re: Fast /tmp (was Re: Mixing paging and IO is inefficient)
Message-ID: <63090@lll-winken.LLNL.GOV>
Date: 28 Jun 90 17:45:13 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>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 14

| From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
| 
| >From: ian@sibyl.OZ (Ian Dall)
| >
| >A mkfs (or newfs) takes of the order of the same time as
| >an fsck anyway. /tmp is usually cleared on a reboot so there is no problem.
| 
| 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.
Berkeley has already implemented a Memory File System and mount /tmp on it by
default.