The following reply was made to PR bin/34979; it has been noted by GNATS.

From: christos@zoulas.com (Christos Zoulas)
To: Scott Ellis <scotte@warped.com>
Cc: gnats-bugs@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org
Subject: Re: bin/34979: -current libc causes boot failure
Date: Sun, 12 Nov 2006 20:02:06 -0500

 On Nov 12,  5:00pm, scotte@warped.com (Scott Ellis) wrote:
 -- Subject: Re: bin/34979: -current libc causes boot failure
 
 | Christos Zoulas wrote:
 | [snip]
 | > It gets a blank line from intrepid; prog is empty, so the strlen() in the
 | > loop does not advance...
 | [snip]
 | 
 | Yeah, but why does it get that input on the first run through?  Because 
 | it's pulling data from the message buffer (those first lines look like 
 | the log from booting), and subsequent runs have "real" syslog messages 
 | in there?
 
 Yes, I think so. The question is who added the empty line on the x86_64 boot
 message that triggers the problem :-)? Or what changed?
 
 christos