I had the exact same problem upgrading to NetBSD-1.4 on a 386 without
FPU.  I just installed it manually instead.  Any idea what might cause
that?  I'd love to give you a core dump, but the filesystem was too smal
for a core dump, and this crappy old machine would croak if I tried to
steal any more RAM for the ramdisk.

Rick

"Perry E. Metzger" wrote:
> 
> Bernd Sieker <bsieker@TechFak.Uni-Bielefeld.DE> writes:
> > I re-downloaded the image and doublel checked the floppies, just to avoid
> > any other sources of problems.
> >
> > After the above message it says "floating point exception". Note that this
> > happened on both Cyrix 486 with 1.3.2 installed and on Celeron with 1.4_BETA
> > installed.
> 
> Ah.
> 
> Does this Cyrix have an FPU?
> 
> > This even happens after completely restoring the old etc. The /sbin/init left
> > on my disk is about 1MB in size, the regular init is only some 170k.
> >
> > Taking a close look, the file called /sbin/init on my / partition after
> > the failed installation _is_ sysinst. Now how could that happen?
> >
> > What's going wrong here?
> 
> All the executable files on the ramdisk boot image are hard linked to
> each other -- its the way we avoid needing shared libs and manage to
> get everything to fit. Sysinst is probably copying these files to the
> hard drive. It is a matter of debate whether it should be doing this
> at all.
> 
> Perry