Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!usc!apple!sun-barr!ccut!kogwy!titcca!cc.titech.ac.jp!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.arch
Subject: Fast /tmp (was Re: Mixing paging and IO is inefficient)
Message-ID: <5696@titcce.cc.titech.ac.jp>
Date: 28 Jun 90 02:16:02 GMT
References: <137770@sun.Eng.Sun.COM> <1990Jun26.152907.979@cbnewsi.att.com> <MOSS.90Jun27085023@ibis.cs.umass.edu>
Sender: news@cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 18

In article <MOSS.90Jun27085023@ibis.cs.umass.edu> moss@cs.umass.edu writes:

>   In general computation, it might be true.
>   In case of temporary compiler output files,
>   isn't it enough just try to "make" again?
>   If something wrong, let's try "make clean" and "make".
>
>   Or did I miss some other important points?

>The problem is that the file system structure itself (inodes, free block info,
>etc.) can get somewhat scrambled, such that it is not even a legal file system
>structure.

In general, it is a problem.

But, in some cases, it is not a problem.

					Masataka Ohta