Description of Problem:
With /tmp mounted as 'tmpfs' file system one can see instances of a random
file corruption for files in /tmp. It is probably the easiest to observe
by doing ./config for a bigger software package. There are pretty good
chances for strange failures recorded in 'config.log' with obviously
corrupted test sources. If /tmp is on disk then ./config does not have
Mounting /tmp as 'tmpfs' works just fine with various 2.4.9-... kernels.
Version-Release number of selected component (if applicable):
At random. I noticed that also on other occasions (extra lines show up
in a text file from /tmp re-read into an editor).
While I don't have corruption reports for tmpfs in 0.4 I have a boatload of
other "it's broke" ones; this was due to a bad patch and should be fixed in
2.4.18-0.12 and later (rawhide/skipjack SE)
Note: We recommend to NOT use tmpfs for /tmp since it's not a complete
filesystem. Some things will break subtly.
Please reopen this bug if 2.4.18-0.12 or later don't fix this.
There is a marked improvement with 2.4.18-0.13 from beta4. Cannot guarantee
all corner cases but things which were giving me troubles before now work
One of possible test cases is 'texconfig' which was unexpectedly aborting
in the middle with 2.4.18-0.4 unless TMP env variable set to some "real"
directory. Now it runs without any hiccups.