Subject: Re: bin/34979: -current libc causes boot failure
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, scotte@warped.com>
From: Scott Ellis <scotte@warped.com>
List: netbsd-bugs
Date: 11/13/2006 01:05:03
The following reply was made to PR bin/34979; it has been noted by GNATS.
From: Scott Ellis <scotte@warped.com>
To: Christos Zoulas <christos@zoulas.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 17:00:38 -0800
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?
ScottE