From owner-freebsd-current@FreeBSD.ORG  Wed Apr  9 19:50:21 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 C5DB737B401; Wed,  9 Apr 2003 19:50:21 -0700 (PDT)
Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au
	[210.50.30.52])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 393E443F93; Wed,  9 Apr 2003 19:50:21 -0700 (PDT)
	(envelope-from tim@robbins.dropbear.id.au)
Received: from dilbert.robbins.dropbear.id.au (203.134.135.18) by
	smtp01.syd.iprimus.net.au (7.0.012)
	id 3E8A144A001DB00F; Thu, 10 Apr 2003 12:50:03 +1000
Received: by dilbert.robbins.dropbear.id.au (Postfix, from userid 1000)
	id 022AAC90D; Thu, 10 Apr 2003 12:49:59 +1000 (EST)
Date: Thu, 10 Apr 2003 12:49:59 +1000
From: Tim Robbins <tjr@FreeBSD.ORG>
To: Giorgos Keramidas <keramida@freebsd.org>
Message-ID: <20030410124959.A92534@dilbert.robbins.dropbear.id.au>
References: <20030408174535.CA3285D07@ptavv.es.net>
	<200304100239.h3A2dLLo072238@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200304100239.h3A2dLLo072238@freefall.freebsd.org>;
	from keramida@freebsd.org on Wed, Apr 09, 2003 at 07:39:21PM -0700
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2003 02:50:22 -0000

On Wed, Apr 09, 2003 at 07:39:21PM -0700, Giorgos Keramidas wrote:

> > From owner-freebsd-current@FreeBSD.ORG  Tue Apr  8 10:45:38 2003
> > To: Scott Carmichael <freebsd@jobeus.net>
> > 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.

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.).


Tim