Subject: kern/2128: nfs v3 puts NULs in files when using >> in sh configure scripts
To: None <gnats-bugs@NetBSD.ORG>
From: John Kohl <>
List: netbsd-bugs
Date: 02/25/1996 19:13:02
>Number:         2128
>Category:       kern
>Synopsis:       nfs v3 puts NULs in files when using >> in sh configure scripts
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 25 19:50:01 1996
>Originator:     John Kohl
NetBSD Kernel Hackers `R` Us
>Release:        NetBSD-current, 1996/02/25
System: NetBSD pattern 1.1A NetBSD 1.1A (PATTERN) #4: Sun Feb 25 09:56:05 EST 1996 jtk@pattern:/u3/NetBSD-current/src/sys/arch/i386/compile/PATTERN i386

I have a configure script which is consistently generating files with
some NULs in them when writing to an NFS v3 mounted disk (from another
NetBSD/i386-current server on the same ethernet).
When I use NFS v2, it does not generate the NULs but generates the
proper output file.

The NUL output appears twice, just before 8k and just before 16k (as if
it is mistakenly filling out the end of a block).

When I change the blocksize to 1k, I get more runs of NULs which
zero-fill to the end of a 1k-aligned block.

The configure script is hard to suck out of context, but if someone
wants to debug this I can put together an example case with the entire
sources in question.

	???  this really sucks.