Re: 'for' unexpected.

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

> > From owner-freebsd-current_at_FreeBSD.ORG  Tue Apr  8 10:45:38 2003
> > To: Scott Carmichael <freebsd_at_jobeus.net>
> > Date: Tue, 08 Apr 2003 10:45:35 -0700
> > cc: freebsd-current_at_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