From owner-freebsd-current  Sun Jan 28  5:36:37 2001
Delivered-To: freebsd-current@freebsd.org
Received: from mamba.cids.org.za (mamba.cids.org.za [146.64.58.49])
	by hub.freebsd.org (Postfix) with ESMTP id 54D2737B400
	for <current@freebsd.org>; Sun, 28 Jan 2001 05:36:18 -0800 (PST)
Received: (from pallenby@localhost)
	by mamba.cids.org.za (8.11.1/8.9.1) id f0SDaAR31229
	for current@freebsd.org; Sun, 28 Jan 2001 15:36:10 +0200 (SAT)
	(envelope-from pallenby)
From: Paul Allenby <pallenby@mamba.cids.org.za>
Message-Id: <200101281336.f0SDaAR31229@mamba.cids.org.za>
Subject: sh can't be exec'd
To: current@freebsd.org
Date: Sun, 28 Jan 2001 15:36:09 +0200 (SAT)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi all

For the last week, each kernel built with fresh source code
cannot exec sh. I've seen a lot of emails about this, but
most were about the "correct" way to rebuild a system.
Is this a problem affecting only me?

Paul


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message