On 2003-04-09 19:39, Giorgos Keramidas <keramida_at_FreeBSD.org> wrote: > Scott Carmichael <freebsd_at_jobeus.net> wrote: > > > 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. Nope. No use. If I let /usr/src/bin/sh overwrite my /bin/sh it bombs out later while installing games/* with the same error. For the moment, I've replaced /bin/sh with a static copy of bash :-( Tim, is this a known problem? Is anyone looking into this already? - GiorgosReceived on Wed Apr 09 2003 - 17:54:07 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:03 UTC