From owner-freebsd-current Sun Jan 28 7:22:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn128.dh.casema.net [212.64.31.128]) by hub.freebsd.org (Postfix) with ESMTP id A232537B400 for ; Sun, 28 Jan 2001 07:22:01 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0SFhbb01705; Sun, 28 Jan 2001 16:43:47 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010128161923.00c74440@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 28 Jan 2001 16:22:09 +0100 To: Paul Allenby , current@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: sh can't be exec'd In-Reply-To: <200101281336.f0SDaAR31229@mamba.cids.org.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >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? I haven't had any trouble. How do you rebuild your system? What is the exact error you get? And (at the risk of sounding stupid) what's the output of ls -l /bin/sh? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message