From owner-freebsd-current  Mon Apr 21 19:17:26 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA06268
          for current-outgoing; Mon, 21 Apr 1997 19:17:26 -0700 (PDT)
Received: from unique.usn.blaze.net.au (unique.usn.blaze.net.au [203.17.53.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA06250;
          Mon, 21 Apr 1997 19:16:52 -0700 (PDT)
Received: (from davidn@localhost)
	by unique.usn.blaze.net.au (8.8.5/8.8.5) id MAA22774;
	Tue, 22 Apr 1997 12:16:42 +1000 (EST)
Message-ID: <XFMail.970422121641.davidn@usn.blaze.net.au>
X-Mailer: XFMail 1.0 [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3.0.1.32.19970421174205.0093ed50@mantar.slip.netcom.com>
Date: Tue, 22 Apr 1997 12:10:51 +1000 (EST)
Organization: Unique Computing
From: David Nugent <davidn@unique.usn.blaze.net.au>
To: Manfred Antar <mantar@netcom.com>, peter@freebsd.org
Subject: Re: You will need to recompile your libc and apps!!!
Cc: current@freebsd.org, toor@dyson.iquest.net,
        (Bruce Evans) <bde@zeta.org.au>, Terry Lambert <terry@lambert.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On 22-Apr-97 Manfred Antar wrote:
 >There is a need to build a new libc to build a new mount, or to build
> >to include the vfork/pipe changes John Dyson made to libc.
> >
> I Did a make world Sunday with current sources and X doesn't work any more
> if i use a libc from last thurs (4/17/96) it works.kernel is also current
> although and old kernel doesn't make a difference.all seemed to work well
> till Sunday when i did make world from X and shut down.All i get is a
> X screen with nothing else.
>       Any ideas


Yes, the "pipe read" problem is back. I'm running a full make world
and kernel from yesterday and xrdb stalls in piperd. Perhaps Peter's
libc fix is better than Bruces after all? :-)

The reason you're getting ony the X screen is that your .xinitrc
hasn't completed. If you look at a process listing, you'll find
xrdb is stalled. If you're not using any preprocessor directives in
your .Xresources file, then add -nocpp to the invocation of xrdb
to avoid the stall. Of course, this is only a workaround.


Regards,

David Nugent - Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-9791-9547  Data/BBS +61-3-9792-3507  3:632/348@fidonet
davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/