From owner-freebsd-current@FreeBSD.ORG Wed Apr 9 20:04:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8FE137B401; Wed, 9 Apr 2003 20:04:49 -0700 (PDT) Received: from thalia.otenet.gr (thalia.otenet.gr [195.170.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C6E843FBF; Wed, 9 Apr 2003 20:04:48 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b183.otenet.gr [212.205.244.191]) by thalia.otenet.gr (8.12.9/8.12.9) with ESMTP id h3A34cmP015569; Thu, 10 Apr 2003 06:04:39 +0300 (EEST) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.9/8.12.9) with ESMTP id h3A34ccK021892; Thu, 10 Apr 2003 06:04:38 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.9/8.12.9/Submit) id h3A34IKN021880; Thu, 10 Apr 2003 06:04:18 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 10 Apr 2003 06:04:18 +0300 From: Giorgos Keramidas To: Tim Robbins Message-ID: <20030410030418.GA21622@gothmog.gr> References: <20030408174535.CA3285D07@ptavv.es.net> <200304100239.h3A2dLLo072238@freefall.freebsd.org> <20030410124959.A92534@dilbert.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030410124959.A92534@dilbert.robbins.dropbear.id.au> cc: freebsd@jobeus.net cc: freebsd-current@FreeBSD.ORG Subject: Re: 'for' unexpected. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 03:04:50 -0000 On 2003-04-10 12:49, Tim Robbins wrote: > On Wed, Apr 09, 2003 at 07:39:21PM -0700, Giorgos Keramidas wrote: > > Using a userland and kernel from Sunday, April 6 2003, I hit this when > > trying to upgrade to today's current too. Unfortunately, rebuilding > > /bin/sh didn't quite work while I was in single-user mode... Probably > > because the file /bin/sh is 'in use'. I've brought my workstation > > up by running while in single user mode: > > > > # exec /bin/csh > > name# cp /usr/local/bin/bash /bin/sh > > name# exit > > > > I'll try rebuilding now. Who knows *why* this happens? I think it > > definitely deserves an UPDATING entry. > > I'm interested and puzzled at why this is happening -- /bin/sh itself hasn't > changed for the past 3 weeks. In the 3 weeks before that, about 4 lines of > code were changed. I suspect a bug in libc or a bug in one of the tools that > generates the shell's parsing code (awk, sed, etc.). Hmmm, something of this sort was probably happening. I replaced /bin/sh with bash for a while, booted single user mode, entered /usr/src/bin/sh and built normally, then replaced /usr/obj/usr/src/bin/sh with /bin/bash *again* (to avoid bombing half way through installworld when the new sh was installed), and let it all finish normally. Rebooted, and now it works. Sorry for the false alarm everyone...