Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!amdcad!snap!ching
From: ching@snap.amd.com (Mike Ching)
Newsgroups: comp.os.minix
Subject: Re: V1.3 cat /dev/null != EOF  ? (have you seen this?)
Keywords: MINIX 1.3  /dev/null does not return EOF when read ?
Message-ID: <28304@amdcad.AMD.COM>
Date: 7 Dec 89 21:51:15 GMT
References: <424@eds1.UUCP>
Sender: news@amdcad.AMD.COM
Reply-To: ching@snap.AMD.COM (Mike Ching)
Distribution: na
Organization: Advanced Micro Devices, Inc. Sunnyvale CA
Lines: 17

In article <424@eds1.UUCP> jdm1@eds1.UUCP (Jon McCown) writes:
-
-Dissecting the library rebuild script ("run") and executing it in
-discrete steps, I noticed that what croaked the process was:
-
-cat /dev/null - newfile
-
-Which seemed innocent enough to me, until newfile (or whatever) grew to
-fill the HD.  I haven't yet gotten into the FS code to look, but has anyone
-seen this before?

I had the same problem and replaced the line with 'rm newfile ; touch newfile'
to create the file. There's another occurance of file creation in "run"
that I fixed the same way. I didn't try to figure out what is broken in
cat.

mike ching