From owner-freebsd-current@FreeBSD.ORG Wed Apr 9 19:39:22 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 4479737B401; Wed, 9 Apr 2003 19:39:22 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E923743FA3; Wed, 9 Apr 2003 19:39:21 -0700 (PDT) (envelope-from keramida@FreeBSD.org) Received: from freefall.freebsd.org (keramida@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h3A2dLUp072239; Wed, 9 Apr 2003 19:39:21 -0700 (PDT) (envelope-from keramida@freefall.freebsd.org) Received: (from keramida@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h3A2dLLo072238; Wed, 9 Apr 2003 19:39:21 -0700 (PDT) Date: Wed, 9 Apr 2003 19:39:21 -0700 (PDT) From: Giorgos Keramidas Message-Id: <200304100239.h3A2dLLo072238@freefall.freebsd.org> To: freebsd@jobeus.net, oberman@es.net In-Reply-To: <20030408174535.CA3285D07@ptavv.es.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 02:39:22 -0000 > From owner-freebsd-current@FreeBSD.ORG Tue Apr 8 10:45:38 2003 > To: Scott Carmichael > Date: Tue, 08 Apr 2003 10:45:35 -0700 > cc: freebsd-current@freebsd.org > Subject: Re: 'for' unexpected. > > > So, anyways, anyone know what this could be? I can't seem to even type > > a 'for' statement in sh and make it work. Eek. > > See the archives. This is a problem reported earlier this week. > > Work around: > cd /usr/src/bin/sh > make clean > make > make install > cd /usr/src > make installworld 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. - Giorgos